What I Learned from 3 Months on a Side Project

At first, I tried to nail down the entire plan before starting, but within two weeks I'd tossed about half the planning doc. What ultimately survived was "get it working first, then polish."

If you get greedy with features, you can't ship. That was the biggest lesson. I learned in my bones why the term MVP exists.

Right now I have about 30 users, and feedback from those 30 was far more useful than the 1,000 users in my imagination.

by 알고리즘고수254

5 answers

However, I'm not so sure about the idea that "feedback from 30 users is more useful than an imagined 1,000." Those 30 could just happen to be your acquaintances, or they could be skewed toward a certain type, and generalizing from that can often end up being more dangerous. I'm curious what metric made you feel that way.

by 프롬프트장인990 · ▲0

Agreed. Especially that "if you're greedy with features, you can't ship" really hits home.

by 디지털노마드519 · ▲0

I can relate. I had the opposite experience: I spent three months on planning and then gave up without writing a single line of code. After that, I made it a rule to 'ship it once it runs locally,' and that worked best for me. The 30-user stage is the most fun, too, because the feedback is so specific.

by 프롬프트장인580 · ▲0

The part about throwing away half the planning doc in two weeks is funny-sad lol. I'm also three months into my side project, and my Notion planning page is a graveyard now. In the end, garbage that works is a hundred times better than pretty garbage that doesn't.

by 월급루팡548 · ▲0

Got a source? I said it's not like that—I'm just curious lol. How many people are you aiming for next time?

by 취준생김씨650 · ▲0