3 ms·
He also told me we would almost certainly need to rewrite everything at least once, so not to dwell too long on the initial stuff. Build the MVP,
by JohnBooty 4y ago
He also told me we would almost certainly need to
rewrite everything at least once, so not to dwell too
long on the initial stuff.
Build the MVP, build it quickly, get it in front of users.
It just needs to work, you're not going to get marks, or
customers, for backend coding style.
1000% agree. Overengineering things is the death of MVPs. But man this is hard to do in many real world situations.
Stakeholders and managers want you to keep adding incremental features. Never had a situation where they were like "okay, cool MVP, see you in a few months after you tear it down and rebuild it 'for real'."
That "build a fast crappy MVP" mentality takes serious buy in from stakeholders from day one. That mentality might be common in SV and other startup communities but boy is it tough to find elsewhere.
- taeric 4y agoAgreed, but it is also easy to see the tension in your second paragraph. You can plan to rewrite everything at least once, but you will never get that actually in the plan. My only somewhat clear path out of it is to make sure you built it so it will be easy to rewrite. Either do the least that you can, or keep an eye for improvements, but don't necessarily act on them.