Armin Ronacher · 2026-07-13 · notable
Armin Ronacher — coding agents may erode the shared architecture big software needs
Armin Ronacher's essay argues coding agents let each engineer ship features in parallel without the coordination — pull requests, review, interface negotiation — that used to keep the whole team's mental model of a codebase in sync.
Armin Ronacher argues coding agents let engineers ship in parallel — which quietly skips the coordination that keeps big software coherent.
What is it?
The Tower Keeps Rising is a July 13 essay by Armin Ronacher — the creator of Flask, Jinja, and Sentry's Rust code — on how AI coding agents change the shape of software teams, not just their speed. Ronacher opens with Bruegel's Tower of Babel and argues that scaling engineering has always required a shared language and a shared mental model of the system; agents remove much of that shared-work friction.
How does it work?
Ronacher's argument follows a causal chain. Human coordination used to be the bottleneck, but that bottleneck also forced synchronization: pull requests, code reviews, and interface negotiations kept everyone roughly on the same page. When any engineer can hand an agent 'add OAuth' or 'add caching' and merge the result without pulling anyone else in, those sync events stop firing. The essay predicts a codebase that keeps growing bigger and more feature-rich while nobody — human or model — still holds the whole system in their head.
Why does it matter?
For engineering leaders, The Tower Keeps Rising reframes agent adoption as an organizational question rather than a productivity metric. Ronacher's warning is that the classic sign of an unhealthy codebase — nobody knowing why a subsystem exists — starts becoming the default state rather than a failure mode. Teams that judge coding agents only by lines shipped miss the coherence tax, and only see the bill when a rewrite becomes unavoidable.
Who is it for?
Engineering leaders, staff+ engineers, and anyone rolling out coding agents at team scale.