5 ms·
The point OP is making is that in a startup, you don't do engineering for the sake of engineering. In the end, what matters is generating wealth. Obviously, yo
by relyio 9y ago
The point OP is making is that in a startup, you don't do engineering for the sake of engineering. In the end, what matters is generating wealth.
Obviously, you want a sane legacy for the future but unless you already have hit that sweet product-market fit spot it is likely that you will spend a non-trivial amount of time optimizing (prematurely) for something that's in fact orthogonal to what you actually need.
The trick, as usual, is to balance engineering and business depending on which stage your at.
- vidarh 9y agoThis, I find, is one of the hardest things about hiring developers for a startup. Because on one hand you want people who knows how to do things right. On the other hand, you want people who are prepared to accept that decisions that are insane in a stable business can be very much rational in a business where the cost of cash to fund large engineering changes is dropping at a crazy rate if you're successful, and doesn't matter if you're not (because you'll never get to it). Of course it's good to avoid completely pointless mistakes. But it often matters far more to deliver.