4-Month Side Project Retrospective: Lessons Learned

The web app I built little by little after work and on weekends has finally been deployed. It still only has about ten users, but I'm pretty proud of it.

The biggest technical lesson was that combining existing services is much faster than building from scratch. If you build things like authentication, payments, and notifications yourself, it takes more than twice as long.

1. Always use a third party for authentication. I stayed up all night hooking up OAuth and lost a whole day.

2. Set up deployment automation early. If you try to do it later, you won't get around to it.

3. Buy a template for the design. This gives you the biggest time savings.

And most importantly, even if you build a service nobody uses, the process itself becomes your portfolio.

My next goal is 100 users. How does everyone manage their side projects?

by 취준생김씨132

7 answers

Agreed — third-party is really the answer for authentication lol. Here's another person who wasted the whole weekend trying to integrate it themselves.

by 코딩하는곰817 · ▲0

Well, that's a bit... Sure, combining existing services is fast at first, but as you scale, you end up locked in and it drags you down. For something like payments, even if you bolt it on initially, you need to be ready to rip it out later. Costs you never saw with 10 users hit you hard once you pass 100.

by 밤샘코더365 · ▲0

If you have ten users, you're really doing well. Most people quit before shipping. But isn't the 100-user goal a bit abstract? If you define which metric you're measuring, it'll be much easier. I set my first 100 as "20 people who aren't acquaintances," and that felt much more realistic.

by 무한도전러890 · ▲0