- Author
- Chad Fowler
- Published
- December 30, 2025
- Kind
- Personal essay in the author's Phoenix Architecture series
- Original
- aicoding.leaflet.pub/3mbaguyrjek2g
- Subject
- Coding with agents
What it is
Chad Fowler wrote this essay as part of The Phoenix Architecture. Fowler recalls writing about trashing servers in 2013. Fowler now applies the same idea to code written with AI.
What it says
- Fowler argues that editing code in place is mutation, and mutation builds hidden cost.
- The phoenix principle: a component must be regenerable from its specification and evaluations.
- Comprehension is now the bottleneck, so understanding an implementation becomes optional.
- What persists across replacement is interfaces, contracts, evaluations, monitoring and data.
- The post says the code is not the asset; the specification and evaluation are.
- Editing code becomes a last resort and a debugging activity, not development.
- Fowler answers objections such as waste, lost optimizations and lost institutional knowledge.
What evidence it gives
The post argues by analogy to immutable infrastructure. It recalls a Wunderlist-era rule that new technology code stay tiny. It gives no measurements and no example of regenerating a real system.
Interests and limits
Fowler publishes the Phoenix Architecture series, so the essay is also its own advocacy. Nothing was tested. The post treats good specifications and evaluations as achievable and does not show how. Other essays in the series were not read.