A field report from a year of orchestrating coding agents on a real product.
Presented at
- AI Engineer Europe, London, May 2026
Evergreens are ideas I've invested significant time into. They are refined, edited, and won't significantly change – aside from the occasional trimming.
One Developer, Many Agents, No Alignment
A field report from a year of orchestrating coding agents on a real product
9 Backlinks
Quiet Interfaces: Designing Software That Knows When to Shut Up
On notification fatigue, ambient signals, and the case for tools that respect your attentionDesign Tokens Are Social Contracts
The technical layer is easy. The agreement between people is the hard partShipping With Agents: Twelve Months of Delegating My Own Job
What changed, what broke, and what I would never hand to a model againThe Blank Page Problem in AI Tools
Chat boxes make everything possible and nothing obviousPairing With a Model Is Not Pair Programming
On the asymmetry of attention, memory, and accountabilityCSS Is a Programming Language, and That Is the Point
Declarative systems reward a different kind of thinkingKeyboard-First Is a Culture, Not a Feature
Notes on who command palettes are really forLegible Systems
On making the invisible machinery of software visible enough to argue withThe Last User Interface
If language models can drive any screen, what is left for a designer to design?Mentions around the web
3 Likes and Reposts
The layout of this site is a pleasure to read on a phone. Also, strong agree on the argument.
Adding this to the list of pieces that convinced me to stop posting to timelines first.
I disagree with the second half, but it is the useful kind of disagreement. Writing a reply post.
Did not mean to write a whole essay, but got on a roll. Corrections welcome.