[ about ]
we are the engine room of the mantro ecosystem.
we are home to hardware tinkerers, software technicians and design afficionados.
[ fundamentals ]
we are wired for high-standard yet pragmatic work results. we craft tailored solutions for the individual situation. we aim to enable progress without establishing codependence.
we are not cutting edge scientists nor do we aspire to be. we work on the future by building technological solutions that solve tangible problems. nothing more, nothing less.
[some of our guiding thoughts]
Our way does not have to align with ”what everybody says”. Also there is no need to feel better than anybody else. Our objective has side-goals that need to be accomplished that might not exist in other settings.
Sounds familiar? Well, sorry to break the news. Both are wrong, and right. Actually it depends on the maturity of the product. Early stage? Maybe don't focus on tests, iterate instead. Late Stage? Well, you better have good tests. Always understand that something might not be important right now… but maybe in the not-to-distant future?
A perfect solution for your local one-man-show tool. A disaster for your backup cronjob. If you can handle only state 1-3, throw an exception with a meaningful message on all other states. Throw in your name, the class, the method and why you cannot proceed anymore.
Well, great. Thing is, I'm out of Uranium and I've never been to outer space. Some companies in the valley (and elsewhere) are operating outside of the normal scale. It's ok to read carefully about their operations and learn, it's ok to think about aspects you can extract form these learnings and put to good use in your own product. But don't cargo cult blindly, especially if you don't have Uranium at your disposal.
That sounds bad. Very bad. We should design systems in a way that we can rely on safeguards. That the process is understandable. That the necessary things are documented. And everybody needs to be able to execute crucial steps. Be it deployment, or bugfixing. Deploy often. Get rid of the fear. Get used to it. Mistakes will be made, shit will hit the fan, yadda yadda. Step up and do it yourself. With the help of others. With supervision. And then, without safety net. Yourself.
This is a very common sentence... in a corporate. You should never find yourself in that situation. Take ownership of what you do. Somebody is leaving? Ask them for a handover, check out the code, read into it. You think somebody is about to do a bad decision? Speak your mind, explain why you see negative implications. You see parts of the code breaking? Come up with a plan on how to tackle it.