I build small software in Seoul, mostly by describing it. I came to code late and from the other side: a team of AI agents does the typing, and I spend my time on what the thing should feel like.
These are my notes on that work, and the occasional longer essay.
NowUpdated Nov 2026
- Building small products with a team of AI agents, and learning to read the code they write.
- Writing one note a week about what broke.
- Reading A Philosophy of Software Design, slowly.
Writing
A stop has to mean stop. If the word only slows things down, nobody will say it early enough.
Zero checks is not the same as passing checks. It took two bad merges in one day to learn the difference properly.
Describe, don’t type

Most of my design feedback is one sentence: this looks like nobody chose it.
Measured what a feature costs to run, in won, before arguing about whether to build it. The argument got much shorter.
What a review is for

Looked at Patrick Collison’s site again. Fifteen plain links and no apology. The confidence is in what’s missing.