2 posts tagged with "engineering-strategy"

Every no-code platform you've ever used was priced against the same benchmark: the cost of hiring an engineer. That was the entire pitch. Writing real software required scarce, expensive people, so the platforms sold you a trade — give up flexibility, accept the walls of the sandbox, and in exchange your ops manager can ship the inventory dashboard herself instead of waiting six months in the engineering backlog. The trade made sense for fifteen years because the benchmark held. Code stayed expensive.

Then the benchmark collapsed. When a coding agent can build and maintain a real application — actual code, in a repository, with a schema you own — for less than the monthly cost of a Retool seat, the drag-and-drop abstraction stops being a shortcut and starts being a ceiling. You're now paying a premium to be prevented from having real software.

But here's the part most obituaries get wrong: the platforms won't die. The smart ones are already pivoting to the thing that was never about the cost of code — governed data access, blessed integrations, and being the sandbox that IT already approved. The constraint on internal tools is moving from "who can build it" to "who's allowed to," and that shift rewrites how you should evaluate your entire internal-tools stack.

For twenty-five years, "never rewrite from scratch" has been the closest thing software engineering has to a commandment. The canonical argument rested on a cost structure everyone took for granted: rewriting means re-reading, re-understanding, and re-typing years of accumulated code, and while you do that, the old system keeps moving and your competitors keep shipping. The rewrite was forbidden because it was slow.

Coding agents just deleted the slow part. An agent can translate a hundred-thousand-line codebase from one language or framework to another in days, not quarters. Teams that ran the numbers on mainframe modernization watched average program costs drop from $9.1 million in 2024 to $7.2 million in 2025, largely on the back of AI-assisted conversion, and consultancies now report 40–50% acceleration on modernization timelines. So the commandment is dead, right? If the expensive part of the rewrite got cheap, the rewrite is back on the menu.

Here is the problem: the typing was never the expensive part. It was just the visible part. The organizations that failed at big migrations rarely failed because the code was hard to convert. They failed on everything around the code — undocumented behavior, data migration, integration cutover, and the operational muscle memory that nobody thought to write down. Agents made the rewrite cheap to start. They did much less for what made rewrites dangerous to finish.