The product builder paradox
The product builder paradox: role collapse works where the customer speaks your language and the solution space is mature. Elsewhere, judgment fragments back.
This is my workshop: a place for ideas to be shaped and refined over time. I write about software, craft, and the ways we might build differently; about small teams that last, tools that respect their users, and a european perspective; about every choice as an arbitrage between competing values.
Design has never been neutral. If that sounds obvious, you'll be at home.
Feel free to browse the existing essays before joining.
Another newsletter A library that grows
Check your inbox for a confirmation email.
Long-form thinking on software and craft.
The product builder paradox: role collapse works where the customer speaks your language and the solution space is mature. Elsewhere, judgment fragments back.
In April 2026, every major AI-coding provider introduced metered overage pricing inside the same window. The pattern is three centuries old. What is new is that the margin capture is arriving before most of the value even arrived.
We want to see into our tools. We do not want our tools to see into us. The current regime has it backwards: opaque technologies, transparent lives. The fix requires both axes: make tools inspectable and make lives unreadable.
There is no best level of openness, only gates designed for their purpose. Open one gate fully and a second one forms where you weren't looking. Design the gate deliberately or its design will be inherited from whoever gains most when it opens.
The interface moat is dead, that's settled. What nobody asked is what opened. AI revealed two independent axes (Scale and Craft) that the interface moat was hiding. Three quadrants survive; one got repriced to commodity. The question isn't whether the moat is dead. It's which quadrant you're in.
Shorter dispatches, by date.
Free essays on building well, delivered when ready.
Check your inbox for a confirmation email.