Give up elevating speed over quality.
“I built this in 48 hours” is merely code for anything that is clumsy, probably has bugs, and has a poor user experience overall. Although I believe it’s fantastic that people are creating stuff, I don’t get this TikTok-level attention span or the haste with which things are being released.
Honestly, investing two years to create your MVP doesn’t ensure any greater success than investing three weeks. Both speed and quality are achievable. The developers and the design are responsible for the quality. not based on the duration.
However, when it fails, I will have no justification. “Well, I didn’t even use THAT much time to build it anyway” won’t help me get over my failure and guilt.
Cost, speed, and quality are all highly correlated.
However, I do believe that a SaaS and a “good” piece of software cannot be achieved with just one landing page and GPT.
If you are seeking to validate your hypothesis, move quickly; if it has already been verified, take your time to refine it so that it outperforms those of your competitors. But I don’t see why you should laud the fact that you made it in just two days.
I concur. Speed has been overly exalted.
In the process of verifying a concept, speed matters. However, not to the point where you launch a terribly bad product and the MVP is viewed as a failure.
Conversely, while working on an issue that has already been solved, quality and method matter much more than just speed. To what extent have you improved the product?This is a question that one ought to be able to respond to.
Yes, I don’t get the appeal of putting speed ahead of quality. It gives me the impression that “I’ll be back once you’ve settled in” in a few months. Continue shipping and grinding; it’s not a race; instead, provide users a polished, non-rushed MVP. Have fun with coding!