“Any sufficiently advanced technology is indistinguishable from magic.” – Arthur C. Clarke
Most developers now write less code by hand. Gergely Orosz recently posted that modern software engineering is no longer done without LLMs and will no longer be done without them. Some miss writing code, while others question how much of the code that agents produce should be read. Writing and reading code gave a lot of developers satisfaction and identity, and as Kent Beck has put it, a sense of competence. I saw this in real time.
Ten years ago, I’d sit at conferences and feel a sense of wonder whenever anyone was brave enough to do a live demo. I felt gleeful when they wrote lines of code, went back to fix mistakes, and made something cool and interesting appear on the screen in front of me. It was magical, and I’m sure that magic is why a lot of developers got into this industry. I can partly understand the sense of loss that people are experiencing. I saw magic, they were in charge of the craft of their code, and that hands-on task has now been given to agents. Where does that expertise go when AI is now writing so much of the code?
As Tim O’Reilly wrote in his recent Radar post, O’Reilly is a business built on cultivating and sharing human expertise. Our job is to find the high ground where that expertise still matters. For developers working in a new world of agentic software factories, I think the expertise you built writing and maintaining software hasn’t gone, it’s just moved. Your expertise now shapes how agents produce software and what evidence you need before we trust the result. To me, AI is enabling you to be magical faster.
Agents amplify whatever you give them, but you need to understand it in the first place. I couldn’t swarm a fleet of agents in the same way a developer can because I don’t have the expertise. You need to understand code. The expertise has gone to a new level of abstraction.
When I spoke recently with Avi Flombaum, the founder of Flatiron School, he agreed that developers’ value was never solely in writing or reading code. AI changes the mechanics, but experience still matters for understanding complex problem domains, articulating what needs to be built, and bringing judgment and ambition to the work. In a separate conversation with Ken Kousen, he pointed out, “We’ve been working with third-party code generators for years; we just called it outsourcing.” This new world of designing AI workflows, setting guardrails, and managing agents much as you would an engineering team, reveals a chance to use accumulated expertise more. It’s your software engineering expertise that matters.
Software factories make this shift especially visible. Companies are now putting agents to work across the development lifecycle, aiming to take work from an initial signal through implementation, validation, and deployment without a person at every step. But generating more code is only part of that process. Without changes elsewhere, you can burn a lot of tokens producing a pile of pull requests that someone still has to review. Anthropic’s AI-native SDLC playbook points out that speeding up implementation shifts pressure onto planning, testing, review, handoffs and approvals, and faster coding tools don’t speed those up on their own. Someone has to understand the whole process well enough to redesign it.
In a software factory, that judgment has to be built into the system. Humans design the workflow, define the conditions under which work can proceed, and decide which exceptions need their attention. Anthropic reports that Claude authors about 80% of the code merged into its codebase, alongside a review process that combines automated checks with human oversight according to risk.
The state of the code matters too. Adam Tornhill and the CodeScene research team found that across C++, Java, and Python codebases, agents working on unhealthy code used 35–45% more tokens to complete the same tasks. That makes refactoring the parts of a codebase agents touch most a sensible investment, but someone has to know which parts those are, decide what “better” looks like, and confirm that behavior hasn’t changed.
Context works the same way. In Port’s testing, giving agents structured context cut costs by about 58% compared with direct access to separate MCP servers. Adding instructions on where to find relevant information pushed the savings to around 80%. Those figures are specific to Port’s experiment, but the work behind them will be familiar to any experienced developer: knowing which relationships in a system matter, and keeping that knowledge accurate as the system changes. Testing tells you whether a particular change works, but evaluating the workflow tells you how reliably it produces acceptable changes and when a person needs to step in.
In Evals for AI Engineers, Shreya Shankar and Hamel Husain describe starting with real traces of what the system did. First comes open coding: reading the traces and writing short notes on what went wrong. Then comes axial coding: grouping those notes into failure categories based on what you actually see. A developer who has spent years debugging production systems will spot the failures that matter and set aside the ones that don’t far faster than someone who hasn’t. That’s where developers’ experience shows up now: in the problems they define, the standards they set, and the evidence they demand before anything ships.
Every shift in every industry has made some people miss the old ways, but the industry has survived. Back in December 2025 I wrote: “AI rewards strong engineering; it doesn’t replace it,” and I stand by that statement. Developers are still magical to me, even when they’re not the ones writing the code. I couldn’t build a software factory myself because I don’t have the years of experience it takes to know where agents should work, how to guardrail them, and how to judge what they produce. The developers who do are the ones I trust to build it. And, as Ben O’Mahony pointed out to me recently, “Those who have a lot of exposure to Agentic engineering have seen past the magic and are back to engineering!” It’s an exciting time to be involved.
Want to understand how to think about engineering craft in this new world? Join Avi Flombaum for his new series, The Agentic Rethink, starting Wednesday, Jan. 13, 2027, on the O’Reilly platform.
