Why I build

Most of what I've built is small. A tool to scratch my own itch. A weekend script. A landing page nobody asked for. A few never made it off my laptop.

I used to be embarrassed about that. The internet rewards loud launches and big numbers, and I had neither.

Then I noticed something. The small ones were the only projects that taught me anything.

The lesson is in the doing

You don't learn to build by reading about building. You learn at the point where the README stops and the real problem starts. Where the API isn't quite what the docs promised. Where the design that looked great in Figma falls apart at 360 pixels wide. Where a user does the exact thing you swore nobody would ever do.

That part isn't in any course. The only way through it is through it.

Small beats theoretical

A finished thing beats a perfect plan. Even a small, ugly one you typed out by hand at midnight. Because it's real. Someone can use it. It can be wrong in interesting ways.

Plans only get to be wrong in boring ways.

So I keep building small things. A few of them grow up. Most don't. But every single one taught me something I couldn't have picked up any other way.

That's the whole reason.