Why AI compilers could make “developer velocity” irrelevant

A recent article by Ray Myers explores how AI agents are making code output cheap, with AI-generated C compiler milestones as proof. He argues the real edge now is shipping correct software through “agent-ready” delivery pipelines.

anthropic cover

TL;DR

  • AI agents make raw code output cheap; code volume no longer signals competitive advantage
  • Bottleneck shifts to confidence and correctness; progress measured by delivery and safe, frequent shipping
  • Agent readiness” tied to Continuous Delivery; pipeline should make a definitive releasability call; environment feedback/back pressure matters
  • Compilers are “easy mode” for agents: pass-as-pure function, clear I/O, and reference compiler as oracle for testing

The premise of “Velocity Is Dead: AI-Generated Compilers and the Future of Software” is simple: AI agents have made raw code output cheap enough that it’s no longer a meaningful competitive advantage—and the industry is still catching up to what that implies for day-to-day engineering.

OpenHands Chief Architect Ray Myers frames the argument around a recent, very concrete milestone: Anthropic’s report that it generated a C compiler—roughly 100K lines of Rust—using coding agents, “mostly” unsupervised, at a stated cost of $20,000 in tokens, and capable of compiling large projects like the Linux Kernel and DOOM. Myers pairs that with a parallel experiment of his own: generating a less complete C compiler, ~40K lines of Go, using the OpenHands agent with Opus 4.5, informed by CompCert as a design reference and tested with csmith.

From there, the post pivots away from tallying lines of code and toward the question that hangs over nearly every “million lines in a weekend” demo: what matters when software is fast to produce but still hard to make reliably correct?

The bottleneck shifts from creation to confidence

A key thread is that the right unit of progress isn’t volume—it’s delivery, and in particular whether a team can merge and ship frequent changes safely. Myers calls this “agent readiness,” and ties it closely to Continuous Delivery, citing the “Minimum Viable CD” framing that the pipeline should make a definitive call on releasability.

He also highlights the concept of environment feedback (or back pressure) as part of what makes agents more effective when the system around them provides rapid, reliable signals.

Why compilers are the “easy mode” for agents

An especially sharp section explains why compilers show up so often as AI-agent flexes: each pass can be treated like a pure function with well-defined inputs/outputs, and there’s often a reference compiler to serve as an oracle. That makes them unusually testable compared to typical enterprise systems with messy side effects and incomplete understanding.

Myers ultimately argues that the industry’s instinct to celebrate “velocity” is outdated—and that the teams that stand out will be the ones optimizing for software that works and processes that keep it working.

Read the original: Velocity Is Dead: AI-Generated Compilers and the Future of Software.

Continue the conversation on Slack

Did this article spark your interest? Join our community of experts and enthusiasts to dive deeper, ask questions, and share your ideas.

Join our community