> "if you don't get physically sick at the quality of the code in your MVP, then you are spending too much time on code quality." While exaggerated, I'd defini

> "if you don't get physically sick at the quality of the code in your MVP, then you are spending too much time on code quality." While exaggerated, I'd definitely agree. If you don't quite know yet where exactly your company will pivot to in the next year or whether the company will still exist, it doesn't make sense to optimize for code quality - but for product-market fit instead. > Everyone always plans to "go back and do it right," but that never actually happens. That "physically sickening" MVP is the product for life. After having raised an 8 M Series A and hiring some more developers and UX experts, we're currently rewriting most of our app code. It's not an automatism that the bad code gets built on for eternity.