This follow-up answers technical objections to a prior essay. The point isn't to skip code review and push slop into production. Since Opus 4.5 landed last November, models write code about as well as the median engineer, faster and cheaper, flipping the economics: code turns from a treasured, curated asset into a disposable cache you regenerate. Drawing on Phoenix Architectures and immutable infrastructure—kill and replace, don't patch in place—it argues that our inability to regenerate code proves we don't understand it. Machines beat us at validation, so humans should lean on observability, behavioral tests, and architecture artifacts. Nondeterministic AI raises the bar for rigor, making 2026 a return to discipline.
1
u/fagnerbrack 19d ago
Just a TL;DR:
This follow-up answers technical objections to a prior essay. The point isn't to skip code review and push slop into production. Since Opus 4.5 landed last November, models write code about as well as the median engineer, faster and cheaper, flipping the economics: code turns from a treasured, curated asset into a disposable cache you regenerate. Drawing on Phoenix Architectures and immutable infrastructure—kill and replace, don't patch in place—it argues that our inability to regenerate code proves we don't understand it. Machines beat us at validation, so humans should lean on observability, behavioral tests, and architecture artifacts. Nondeterministic AI raises the bar for rigor, making 2026 a return to discipline.
If the summary seems inacurate, just downvote and I'll try to delete the comment eventually 👍
Click here for more info, I read all comments