I’ve spent a lot of my profession as each an analyst and a practitioner advising individuals towards “the massive rewrite.” It’s known as second-system syndrome for a cause: You normally throw away years of hidden bug fixes and safety patches only for the sake of “cleaner” code. However after sitting down with Cloudflare’s Dane Knecht (CTO) and Steve Faulkner (engineering director) to debate their undertaking vinext, it’s clear that the outdated guidelines of technical debt are being rewritten by agentic software program improvement.
Actuality Verify: The Finish Of Monkey Patching
For the final 18 months, the Cloudflare neighborhood relied on OpenNext to run Subsequent.js on their infrastructure. It labored, however as Dane famous, it wasn’t a first-class expertise. “It was a hack, you already know, in a way … the place you’re sort of monkey-patching it to attempt to work elsewhere.”
In a standard software program improvement lifecycle, you reside with that technical debt as a result of a rewrite is just too costly or impractical. However Cloudflare took a distinct path. By transferring to a totally agentic workflow (the place, as Dane put it, “no [human] palms have been on the keyboard”), they rebuilt the framework from first ideas.
The consequence? A codebase that’s smaller, sooner, and optimized for a world the place developer expertise typically takes a again seat to agent expertise (AX).
A New Rhythm: The three A.M. Barbell
The world (myself included) has turn out to be obsessive about how AI modifications the rhythm of labor. Steve shared one thing that ought to make each engineering chief pause: His workflow has turn out to be “barbell-shaped.”
“Both I had very quick like 5–10-minute periods focused at an issue or these like 5–6-hour-long periods,” Steve defined. However the true shocker was when he checked his session information: He observed his peak token utilization was typically at 3 a.m.
“I’m not awake at 3 a.m.,” Steve advised me. “I’d simply brain-dump … right here’s 5 issues to go work on whereas I’m asleep and, like, see how far it will get.”
That is the shift from “supervisor” to “dispatcher.” Steve emphasised that he isn’t a “100x engineer” — he’s an engineering supervisor who has realized to handle brokers in parallel whereas he sleeps.
The “Mirror Drawback”: AI Inherits Our Human Challenges
An fascinating second of the undertaking was a safety oversight that completely illustrates a core problem with agentic improvement. Throughout the preliminary rewrite, the AI brokers repeated the very same safety vulnerabilities (CVEs) discovered within the unique Subsequent.js supply code.
“AI is extra humanlike than you anticipate in a variety of methods,” Dane noticed. “It made the identical errors that they made once they have been writing it initially.”
He famous that this one change to their prompting would have drastically improved the undertaking’s safety profile: “Please evaluation all previous CVEs on Subsequent.js and be sure that we’re not weak.” It was a lesson in context. Whereas the AI missed vulnerabilities at first as a result of it was mimicking its coaching information, Dane famous that when they pointed it to the fitting corpus of knowledge, it “instantly recognized them and was in a position to repair them.” The takeaway for the maturity curve is that agentic outcomes are a mirrored image of the context you present. If you happen to don’t explicitly take motion to keep away from your previous errors, brokers will recreate them with excellent, automated effectivity.
The Maturity Curve: Biased Towards The Merge
Maybe essentially the most fascinating takeaway is Steve’s philosophy on merging code. Many organizations are gun-shy about merging, as a result of fixing manufacturing is pricey.
On this case, Cloudflare is doing the other. “That’s been our default … we’re sort of, like, biasing towards merging,” Steve stated. “We simply know that there are bugs. We all know there’s gaps. We all know there’s stuff that’s acquired to get fastened. So we’re simply trusting that the neighborhood comes up with good options.”
This works as a result of the price of an agentic repair is close to zero. If a bug is discovered, an agent triages it, writes the repair, and submits a pull request. Are we reaching a degree of maturity the place the velocity of correction is extra precious than the understanding of the commit?
Put together For AX
Steve made a remark that may follow me for a very long time: The vinext repository is definitely troublesome for a human to navigate. “If you happen to’re not interacting with this repo with AI, you’re going to have a foul time,” he warned. “It’s truly actually not designed for you. It’s designed for AI-first approaches.”
This can be a key a part of AX: As we transfer additional up the maturity curve, we should begin constructing environments the place brokers can thrive.
A lot of the chatter on this area is about how AI could make builders extra productive. The trail to agentic ROI begins with the belief that sunk price and technical debt imply one thing completely different immediately than it did up to now — particularly when you’re courageous sufficient to let the brokers take the keyboard.
