Why I Write

Writing is how I figure out what I actually think.

That’s it, really. Everything else — the essays, the technical pieces, the short scrappy field notes — comes from that one thing.

I’ve had ideas that felt solid for months. Turned them over, stress-tested them in my head, felt pretty confident. Then tried to write them down and found the gaps immediately. The writing doesn’t just capture the thought. It finishes it. Sometimes it kills it. Both are useful.

This site is where that happens in public.

Some of what’s here takes a long time and makes arguments I’ll stand behind. Some of it is technical — practical, specific, close to the work. Some of it is short and half-formed, and that’s deliberate. Not everything needs to resolve. The field notes especially — they’re thoughts before they’ve hardened into opinions. A thinking space more than a publishing platform.

It’s not a content strategy. There’s no posting schedule I’m going to pretend to stick to. I’m not building a brand. I’m a front-end developer who cares about craft, about how the industry works and why it often doesn’t, and about building things that last. That’s what you’ll find here.

If something’s useful, good. If it makes you think differently about something, even better.

But mostly I write because not writing makes the thinking worse. This is the fix for that.