there's a question i get asked a lot: why spend your weekends building things nobody asked for?
the honest answer is that side projects are the only place where you get to be wrong fast. at work, slowness has a cost. on a side project, shipping something broken on a saturday and fixing it on sunday teaches you more than a month of careful planning.
the feedback loop is different
when you build for yourself, you feel every rough edge. the API that needs three retries. the dashboard that loads too slow. you don't have to imagine the user — you are the user.
that sharpens your instincts in a way nothing else does.
building in public forces clarity
writing a README or posting a launch tweet forces you to explain what you built and why. that exercise alone filters out half the bad ideas before they waste too much of your time.
i like the constraint
a side project has real constraints: limited time, no team, no budget. those constraints push you toward simplicity. you build only what matters. you cut scope ruthlessly. that's a skill.
anyway. if you've got an idea sitting in a notes app, just start. the worst thing that happens is you learn something.