Why I build

Most of the things I've built are small. A scratch-your-own-itch tool. A weekend script. A landing page nobody asked for. Some never made it past my local machine.

I used to be embarrassed by this. The internet rewards loud launches and big numbers, and I had neither. But somewhere along the way I noticed something: the small things were the only ones that taught me anything.

The lesson is in the doing

You don't learn to build by reading about building. You learn by hitting the part where the README ends and the actual problem begins. Where the API isn't quite what the docs promised. Where the design that looked great in Figma falls apart on a 360px screen. Where the user does the thing you swore they would never do.

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

Small > theoretical

A finished thing — even a small, ugly, hand-coded thing — beats a perfect plan. Because the finished thing is real. It can be used. It can be wrong in interesting ways. Plans only get to be wrong in boring ways.

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

That's the whole reason.