I like the article. I am the kind of person who thinks things hundreds times before acting, so it would probably taken me weeks just to settle for an architecture which would probably been overkill for an MVP.
Lesson to learn: not everything should be planned as a complex enterprise app.
They key here, he started with the customer relationship, and built software to support it.
Most engineers try to start with software, and build a customer relationship from what they've built. Most of the time they find they built the wrong thing.
This, sir, is 100% true. This was never a software company, but a food delivery company that happened to run on software.
The customers and the delivery guys willing to jump on right away were the true assets and no, you can't build those relationships on a single weekend.
You might enjoy this video, Stanley Tang of DoorDash talking about how they got their first few orders... masterclass in 'minimum amount of initial work to validate a concept'.
https://www.youtube.com/watch?v=oQOC-qy-GDY
As a songwriter I really suffer from analysis paralysis, and what kinda helped me was to write a song a day for a month. I'm still not a prolific song writer by any means, but it helped me learn that perfect is the enemy of good enough, and that iteration is a lot easier than trying to perfect something the first time.
Yes!! With music I used to debate whether I should do A or B, and spend a long time debating whether I wanted an album of genre A or genre B.. and then not write anything. Now I write both, one (or both!) will sound how I wanted, and then move on
Lesson to learn: not everything should be planned as a complex enterprise app.