On the one-year anniversary of coining “vibe coding,” Andrej Karpathy proposed changing it with “agentic engineering.” The excellence he drew was exact: vibe coding is describing what you need and accepting what comes again. Agentic engineering is designing the system, specifying the constraints, and utilizing AI to speed up implementation you will have already reasoned by. One is expression. The opposite is engineering.
Most software program organizations are operating each concurrently and calling them the identical factor. That’s the place the costly errors are coming from.
Certainly one of my improvement leads put it plainly — not as a coverage place, however as an empirical commentary. In his expertise, vibe-coded PRs persistently arrive lacking edge case dealing with, error paths, and exception logic. Not as a result of the AI forgot them.; it’s as a result of the developer by no means specified them. They described an final result, accepted what the agent produced as a result of it seemed proper, and submitted it. The assessments go as a result of they have been written in opposition to the code that exists, not in opposition to the conduct the system truly requires.
The agent didn’t make one thing up. The developer didn’t know what to ask for.
His response is to not reject AI coding instruments. It’s to require that engineers reveal they perceive what was generated — the sting circumstances, the scaling assumptions, the failure modes — earlier than the PR will get merged. In case you can’t clarify why the answer is designed the way in which it’s, you didn’t design it. You accepted it.
He’s proper. And the information backs him up. PR evaluation instances on closely AI-assisted groups are up 91% — not as a result of AI is writing worse code, however as a result of reviewers at the moment are accountable for reconstructing the comprehension that the developer skipped. That may be a tougher evaluation, not a better one. And it’s compounding.
What AI Did to the Roles — and What It Didn’t
There’s a widespread assumption amongst know-how leaders that AI coding instruments collapsed the excellence between who builds and who opinions — that the agent writes properly sufficient that the previous high quality gates are a legacy of a slower period.
That assumption confuses velocity with comprehension.
The developer, the tester, the architect — these roles have been by no means primarily about producing artifacts. They have been about understanding the system properly sufficient to know when one thing was improper earlier than it grew to become another person’s drawback. The developer who spots a race situation noticed it as a result of they understood the execution mannequin. The tester who asks “what occurs when the consumer does the sudden factor?” requested it as a result of they reasoned by the system’s conduct. The architect who acknowledges that this resolution works now and can break at scale acknowledged it as a result of they held the entire system of their head.
These should not manufacturing duties. They’re comprehension duties. You can’t delegate comprehension to an agent.
What modified is you could now produce 100 traces of code with out having executed the pondering {that a} hundred traces of code used to require. The output exists. The understanding behind it could not. An engineer reviewing a vibe-coded PR just isn’t reviewing code — they’re attempting to reconstruct whether or not the developer who submitted it truly understood what they have been constructing.
The roles should not dissolving. They’re being stress-tested. The developer who designed the answer — who can clarify each edge case, each failure mode, each scaling assumption — is extra helpful than earlier than. The one who accepted what the agent produced as a result of it seemed proper and the assessments handed is now a legal responsibility on the pace the group is transferring.
Three Failure Modes Engineering Managers Must Watch For
These should not hypotheticals. They’re patterns repeating throughout organizations deploying AI coding instruments at scale.
The inexperienced pipeline drawback. A inexperienced pipeline means the code does what it was requested to do. It doesn’t imply the developer requested the correct factor, or requested utterly sufficient. A senior engineer is aware of to look behind the inexperienced. A supervisor who has stepped too removed from the work can’t inform from a dashboard whether or not inexperienced means secure or means quick and unexamined.
The lacking path drawback. The developer who doesn’t perceive the system’s failure modes can’t specify them. The agent can’t floor what the developer didn’t know to require. In a manufacturing system, the glad path is the place issues work. The sad paths are the place you discover out what the system is definitely manufactured from. AI brokers, as Karpathy famous, have been purpose-built for the primary 80% of an utility — the implementation that flows naturally from a well-described intent. The final 20% — the sting circumstances, the failure restoration, the scaling constraints — requires a developer who has truly thought by the system. That 20% is the place vibe-coded code persistently runs out.
The boldness calibration drawback. AI-generated code reads as authoritative. The construction is clear, the naming is coherent, the feedback are current. It doesn’t appear to be code written by somebody who was unsure — even when the underlying logic comprises a guess that one thing won’t ever occur. Human code carries the fingerprints of doubt: the remark that claims “TODO: deal with this case,” the defensive examine that indicators the developer was unsure. AI code usually lacks these indicators. Reviewers have to produce the doubt themselves. That requires judgment the reviewer can solely train in the event that they perceive the system properly sufficient to know what to doubt.
What Engineering Leaders Must Do In another way
There’s a model of technical management that sounds subtle and is quietly harmful on this surroundings: the supervisor who has stepped again from the code to concentrate on supply metrics, who measures the AI program by velocity numbers and adoption charges, and who interprets a senior engineer’s insistence on deep code evaluation as resistance to vary.
That supervisor is optimizing for the output of the method reasonably than the standard of the judgment being utilized to it. In a fast-moving AI surroundings, that could be a compounding error.
Technical proximity just isn’t micromanagement. It isn’t writing code or reviewing each PR. It’s being shut sufficient to the precise conduct of the programs you’re accountable for you could inform the distinction between a crew transferring quick as a result of they’re disciplined and a crew transferring quick as a result of they skipped the laborious half.
The supervisor who can’t learn a PR doesn’t must evaluation each one. However they should perceive what their senior engineers search for after they do. That distinction — between “this handed the assessments” and “that is proper” — just isn’t out there from a abstract. It’s out there from contact.
My crew runs three rituals that don’t have anything to do with standing updates and all the things to do with sustaining that contact.
Two hours each week in an structure working session. Two hours each different week in dash planning. Two hours every dash demoing to the entire crew.
The structure classes are the place the system’s reasoning lives — not the tickets, not the documentation, however the dwelling dialog about why issues are designed the way in which they’re and what the choices have been that weren’t taken. A supervisor who sits in these classes for six months builds a working mannequin of the system that no dashboard can replicate.
Dash planning is the place the disconnects floor. We use planning poker — everybody estimates independently earlier than the reveal. When estimates diverge sharply, the dialog that follows is nearly all the time essentially the most helpful one of many dash. Not as a result of we’re negotiating a quantity. As a result of divergent estimates imply divergent psychological fashions. Somebody thinks this process is a 2. Another person thinks it’s a 13. That hole just isn’t a disagreement about effort. It’s proof that two persons are not trying on the identical drawback.
Divergent estimates don’t measure complexity. They measure the place your crew’s understanding of the system breaks down.
The demos hold everybody trustworthy about what was truly constructed versus what was supposed, cross-train the crew throughout what every particular person is engaged on, and provides the supervisor an important sign of all: whether or not the individuals constructing the system can clarify what they constructed and why the tradeoffs they made have been proper.
An AI agent can produce a demo. It can’t clarify its reasoning underneath questioning. The engineers who can are those you can not afford to route round.
Karpathy’s reframe from vibe coding to agentic engineering just isn’t a terminology replace. It’s a skilled obligation.
The organizations that ignore AI will fall behind. Those that vibe it is going to ship failure at scale. Those that engineer it — intentionally, with comprehension at each layer — are those constructing one thing value operating in manufacturing.
That’s not a productiveness dialog. That may be a accountable AI dialog. The code seems to be completed. The pipeline is inexperienced. The PR is open.
Whether or not it’s truly prepared continues to be a human name. Make sure that your crew — and also you — are shut sufficient to the work to make it.
