I don’t write because I’ve figured something out. I write because I haven’t, and the writing is how the figuring happens. A vague intuition stays vague until I’m forced to put it in order, sentence after sentence, and discover where it falls apart.
This is why the writing here sits next to the work, not in some separate blog. The essays and the projects are the same activity in two registers — both are me trying to think clearly about how software should feel, one in prose and one in code.
I don’t write because I’ve figured something out. I write because I haven’t.
Most of these pieces are unfinished thoughts, and that’s the point. If I waited until I was sure, I’d never publish anything. So I publish the figuring-out, and sometimes a reader writes back with the part I was missing.