Why I Write

I've been building things for a long time, but I haven't written much publicly. That was a gap I felt more than I admitted: ideas lived in meetings, docs, and half-finished notes, and rarely made it out into the open.

Writing is thinking

The main reason I write is selfish: it forces clarity. Sometimes I'm turning something I heard into notes I want to keep; sometimes I'm up against a concept I need to understand—writing it out really helps. I bought a paper-like tablet for exactly that, because I was burning through paper, and after a few weeks each notebook would end up shelved on my desk, only to become nostalgia fuel when I'd open it again two years later. When you try to explain something in writing, you quickly discover the gaps in your understanding. The act of writing is the act of thinking.

There's a quote that captures this:

"We do not write in order to be understood; we write in order to understand." — C.S. Lewis

What you'll find here

The archive has settled into a few lanes, but the through-line is the same — stuff I'm actually working through, not a content calendar.

• Writing — Longer essays on work, craft, and what it costs to care deeply about what you build. The reflective pieces; the ones that don't fit neatly in a PR description.

• ML — Notes from building with models in the real world: agents, evaluation, tool use, and the moment a capability stops being a demo and becomes a trust boundary.

• Systems — When something breaks in a way that scaling alone can't fix — coordination, quotas, APIs, throughput and the stories behind the fixes.

• Math — Occasional primers and re-derivations when I want to understand an idea from the ground up.

• Notes — Shorter sketches when a full essay isn't the right container.

I'm not aiming for a publishing schedule. Let's see where this goes.