Why the user interface is the last to become regenerative

Single-developer capability isn’t a productivity story. It’s the test that tells you whether your architecture is worth keeping.

Why Regeneration Does Not Mean Starting Over

As I mentioned in a previous post, at Wunderlist, we had a rule: any new service had to be "this big", a constraint I'd demonstrate by holding my fingers a few inches apart. The metric wasn't about lines of code. It was about replaceability. If a service w...

Why behavior outlives implementations

Better shapes beat better prompts

Why AI makes the hidden economics of software unavoidable

Not all software should change at the same speed. This has always been true, but it's easy to forget when tools make change frictionless. Generative AI dramatically lowers the cost of modification, which creates a dangerous illusion: that everything can ch...

Programming didn't die all at once. There was no single moment, no dramatic obsolescence event. Instead, something quieter happened: the core constraint that shaped software for seventy years dissolved. Writing code stopped being the hard part.

Software is entering a strange new phase. For most of its history, code was expensive to produce and cheap to keep. We treated it like a durable asset: written carefully, maintained lovingly, upgraded cautiously. Whole professions, identities, and institut...