Comment by somsak2
2 years ago
Maybe spending 30 minutes on one bug is worth it, maybe not. If you're pre-revenue / pre-product-market-fit and you compound tens to hundreds of these 5s to 30m decisions, you're risking running out of time or money before anyone even uses your product.
I would argue it's much worse "engineering" to have no product at all.
> pre-product-market-fit
Is that a euphemism for wandering around aimlessly? committing random code to see what works? That's also not good engineering....
Not saying it won't end in the outcome you want people gamble all the time, I'm just saying it's bad engineering.
I mean, the default of any new company is pre-product-market-fit, no? How else could you start something new? During such an early stage much of your code may be written as a very rough MVP that you're only really using to validate a concept. Sometimes, you're going to just have to trash all of it because the idea was totally wrong and people don't actually care about the problem you're solving.
Those, among others, are the types of cases where spending extra time getting something exactly right (even if just a few hours) is just not worth it.
No, the vast majority of companies are entering a mature market with a product that is based on what the market wants, but with their own value proposition.
It seems that only in Silicon Valley startups and the like do people start companies with only the vaguest idea of what they are actually going to build and no idea of whether or not they're solving an actual problem that anyone cares about.