Subscribe. New essays land in your inbox (and in your ATProto feed) via Leaflet.
Subscribe on Leaflet RSS- SaaS Isn’t Dead. Sameness Is.August 24, 2026
- Most of Your Architecture Was Just Expensive CodeAugust 21, 2026
- The Specification Is Not a DocumentAugust 19, 2026
- When Does a Specification Become a Program?August 11, 2026A spec can contain prose, tests, schemas, formal models, even executable code. The useful boundary is not the syntax but, rather, what survives: if you throw the implementation away, what has to remain so you can build the next one?
- The Implementation RemembersJune 14, 2026Every mature system is carrying around lessons that were never written down. They’re encoded as validations, retries, timeouts, workflows, and exceptions. The implementation remembers. The organization forgets
- Production Is a Compiler InputApril 20, 2026
- The Phoenix PrimitivesApril 13, 2026The architecture of a regenerative system is defined entirely by what you can't delete.
- The Generative StackApril 7, 2026Trying to find the best tool or platform for generative software in 2026 is a mistake that could haunt you for decades
- The Conversation Is the CommitMarch 26, 2026
- Compile to ArchitectureMarch 6, 2026For a long time we’ve treated frameworks as the target of software development. But if systems are meant to be regenerated and replaced safely, the real compilation target has to be the architecture itself.
- The Regenerative GrainFebruary 19, 2026In 2014 I gave a talk called Tiny (keep things small enough to understand) In 2026, small means something different. Small means safe to delete. New in the Phoenix Architecture series: The Regenerative GrainI
- The Industrialization of Regenerative SoftwareFebruary 12, 2026
- The Deletion TestJanuary 24, 2026
- UI Is a Conservation LayerJanuary 21, 2026Why the user interface is the last to become regenerative
- Provenance Is the New Version ControlJanuary 13, 2026
- n=1 Is a Design Constrain (Not a Staffing Model)January 7, 2026Single-developer capability isn’t a productivity story. It’s the test that tells you whether your architecture is worth keeping.
- Relocating RigorJanuary 6, 2026The Discipline That Looks Like Recklessness
- The System Is the AssetJanuary 5, 2026Why Regeneration Does Not Mean Starting Over
- Conceptual Mass and the Compaction DisciplineJanuary 2, 2026
- Immutable Infrastructure, Immutable CodeDecember 30, 2025Why "Never Upgrade in Place" Now Applies to Software
- Evaluations Are the Real CodebaseDecember 29, 2025Why behavior outlives implementations
- The Gradient of TrustDecember 28, 2025Better shapes beat better prompts
- Compaction Is a Financial StrategyDecember 27, 2025Why smaller codebases win in the AI era
- Code Was Never the AssetDecember 24, 2025Why AI makes the hidden economics of software unavoidable
- Pace Layers and AI IntegrationDecember 23, 2025
- The Death and Rebirth of ProgrammingDecember 22, 2025Programming 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.
- Regenerative SoftwareDecember 21, 2025