3 ms·
The issue is, people rarely build the right product on the first try. Your reasoning here assumes that the thing you've spent time building well was the right t
by dkural 10y ago
The issue is, people rarely build the right product on the first try. Your reasoning here assumes that the thing you've spent time building well was the right thing to build. It's worth getting things out quickly initially to find out if anybody wants it. You don't want to compromise the experience of your product (external). Thus it's best to sacrifice features and reduce complexity, in order to test ideas and the quality of product experience. Writing code is just a means to this end.
- eridius 10y agoYou're talking about something completely different here. Putting out an MVP is not the same thing as writing sloppy code that becomes a maintenance burden later.