Vibe coding vs agentic engineering: the difference is whether you read the code

If you've seen the phrase "from vibe coding to agentic engineering," you've seen one of 2026's breakout searches. It sounds like a career ladder — as if "vibe coding" is the kiddie pool and "agentic engineering" is the deep end you're supposed to graduate to. The reality is simpler and more useful. Both terms describe getting AI to write your app. What separates them is a single habit, and it's one you can adopt today without changing tools.

Where the two words came from

Both came from the same person. Andrej Karpathy coined vibe coding in a February 2025 post: "There's a new kind of coding I call 'vibe coding', where you fully give in to the vibes, embrace exponentials, and forget that the code even exists." It was never meant as a methodology — he later called that post "a shower of thoughts throwaway tweet."

A year on, with AI tools far more capable, Karpathy proposed a more serious name. As The New Stack reported in February 2026, he wrote that his "current favorite" was agentic engineering: "'agentic' because the new default is that you are not writing the code directly 99% of the time, you are orchestrating agents who do and acting as oversight — 'engineering' to emphasize that there is an art & science and expertise to it." The developer Simon Willison, who had floated "vibe engineering," conceded in February 2026: "It looks like the term 'Agentic Engineering' is coming out on top for this now."

The actual difference: do you look at the code?

Strip away the vocabulary and one line does all the work. On the Lex Fridman podcast, DHH defined vibe coding like this: "you tell an agent to build software for you. You do not look at the implementation. That, to me, is what separates vibe coding from programming." Karpathy's definition of agentic engineering is the mirror image — "orchestrating agents… and acting as oversight." One phrase says don't look; the other says oversee. That's the whole difference.

Notice the row that doesn't change: either way, you own the app, the data in it, and the bill when it gets busy. No label moves that.

Which one are you actually doing?

Be honest about the habit, not the aspiration. If you take what Lovable or Bolt hands you and ship it without reading it, that's vibe coding — by DHH's own definition. If you read what it wrote, ask it to find the holes in its own work, and push back when something looks off, you're doing the thing Karpathy calls agentic engineering, whether or not you can write the code yourself.

The good news for a non-coder: the upgrade is a habit, not a degree. You don't have to hand-write anything to start looking. Two moves do most of it: reading AI code without coding — three things to check in any diff — and the verify loop, where you make the model attack its own answer before you trust it. Do those, and you've crossed the line the jargon is pointing at.

Does the word matter for you? Not much.

Here's the deflating part: in search, "vibe coding" is still far more common than "agentic engineering," and interest in the newer term actually peaked in mid-2026 and fell back. Experts adopted "agentic engineering"; the wider world kept saying "vibe coding." Even DHH, who does exactly what the term describes, dislikes it — on the podcast he said he "hate[s] that term" and wanted something "as plain as programming, but [that] encapsulates the fact that it's with agents." He'd rather just call it programming with agents.

So don't chase the vocabulary. The useful takeaway is behavioral: the more capable your tools get — and after DHH's "pencils down" moment they're getting capable fast — the more the habit of looking is what separates an app that's fine from an app that quietly leaks. Everything that habit protects is in the guide to shipping a vibe-coded app.

This page has no affiliate links or sponsored placements. Quotes are taken from the published transcript, from The New Stack's report of Karpathy's post, and from Simon Willison's own page; where a term's exact first date is uncertain, this piece says so rather than guessing.