The Guy Who Named It Says It's Already Evolving

Exactly one year ago, Andrej Karpathy posted on X: "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."

That phrase rewired how an entire industry thought about AI-assisted development. We wrote our own Vibe Coding Manifesto about it. The term showed up in MIT Technology Review's 2026 Breakthrough Technologies list. It became shorthand for a genuine shift in who could build software and how.

On February 5, 2026, Karpathy posted again. This time with a course correction.

"Programming via LLM agents is increasingly becoming a default workflow for professionals, except with more oversight and scrutiny." He said many people had tried to name what comes after vibe coding, and his favorite was "agentic engineering."

His reasoning: "'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."

This isn't just a rebrand. It's an acknowledgment that vibe coding hit a wall, and the industry needs something more rigorous to get past it.

What Changed in 12 Months

When vibe coding took off in early 2025, the appeal was obvious. Describe what you want. AI writes it. Ship it. Don't even read the code if you don't want to. For prototypes, personal projects, and quick experiments, it was revolutionary.

Then people started building real things with it.

The quality problems surfaced fast. GitClear's analysis of 211 million lines of code found AI-assisted development produces 60% less refactored code and 48% more copy-paste patterns. Code co-authored with AI contains 1.7x more major issues and 2.74x more security vulnerabilities.

Teams lost understanding of their own systems. Software researcher Margaret-Anne Storey coined "cognitive debt" to describe the growing gap between what AI builds and what teams actually understand about their systems. Simon Willison, one of the most respected voices in the developer community, admitted he'd "gotten lost in his own AI-assisted projects."

Open source maintainers revolted. cURL shut down its bug bounty after AI-generated submissions hit 20%. Ghostty banned drive-by AI contributions. tldraw closed all external pull requests. The term "AI Slopageddon" entered the vocabulary.

Vibe coding works for getting started. It doesn't work for building things that last. Karpathy saw that, and he gave the next phase a name.

Vibe Coding vs. Agentic Engineering

The difference isn't subtle.

Vibe coding says: prompt the AI, accept what comes back, ship it. The developer is along for the ride. Understanding the code is optional. The vibe is the product.

Agentic engineering says: orchestrate AI agents to plan, write, test, and ship code under structured human oversight. The developer is the architect. Understanding is mandatory. The engineering is the product.

In practice, agentic engineering looks like this:

You design the architecture first. Before any AI writes a line of code, you define the system structure, the interfaces, and the constraints.
You break work into well-defined tasks that agents can execute independently.
You run multiple agents in parallel, each working on isolated pieces of the system.
You review everything. Not just "does it compile?" but "does this fit the broader system design and does anyone on the team understand why?"

Anthropic's agentic coding trends report found developers integrate AI into 60% of their work while maintaining active oversight on 80-100% of delegated tasks. That's the ratio. AI does most of the writing. Humans maintain all of the understanding.

The Tools Have Caught Up

Part of why agentic engineering is viable now is the tooling matured dramatically in the past year.

Claude Code turned AI-assisted development into a terminal-first workflow where you can run multiple agent sessions in parallel on complex multi-file refactors. OpenAI Codex launched as a standalone app that clones your repo, makes changes, runs tests, and hands back clean diffs. Cursor became the default IDE for 40,000 NVIDIA engineers. GitHub Copilot added autonomous agent mode. Devin and Windsurf pushed fully autonomous coding further.

But the tool that matters most is the one between your ears.

MIT Technology Review named "generative coding" a 2026 breakthrough technology, noting that AI now writes roughly 30% of Microsoft's code and more than 25% of Google's. Mark Zuckerberg said he wants most of Meta's code written by AI agents. The scale is real.

But MIT also noted the core challenge: AI-generated code that looks plausible may not do what it's designed to do. Tools generate code. Engineers verify it works.

What This Means If You're Not a Developer

I know a lot of our readers aren't writing code themselves. Here's why agentic engineering still matters to you.

The barrier between "people who build software" and "everyone else" is dissolving. Domain experts in marketing, operations, finance, and design are starting to build their own tools and automations using AI agents. You don't need to understand Python. You need to understand your problem well enough to direct an agent.

But directing an agent is a skill. This is the "engineering" part of agentic engineering. It's not just prompting. It's knowing how to break a problem into pieces, define what "done" looks like, and evaluate whether the output actually solves the problem. Those are transferable skills from any professional domain.

The cost of building just dropped again. Work that took weeks can now happen in days. One enterprise customer completed a project estimated at 4-8 months in two weeks using agentic coding tools. Zapier deployed agents at 97% adoption across their engineering team. Rakuten hit 99.9% accuracy on modifications to a 12.5 million line codebase in 7 autonomous hours.

The AI agents market is projected to grow from $7.84 billion in 2025 to $52.62 billion by 2030. This isn't a fad. It's infrastructure.

Where We're Headed

The trajectory from the last 12 months tells a clear story.

Phase 1 (2025): Vibe coding. "Just let the AI write it." Revolutionary for accessibility. Terrible for sustainability.

Phase 2 (2026): Agentic engineering. "Orchestrate AI agents with human oversight." Better quality. Still requires judgment and expertise.

Phase 3 (ahead): We'll see. But the pattern is clear: every wave of AI-assisted development gets more powerful and more structured. The "just prompt and pray" era lasted about a year before the industry demanded rigor.

If you're building with AI right now, whether it's software, content, or business processes, the lesson from vibe coding's evolution applies universally. Speed without structure creates debt. Speed with structure creates value.

The vibes got us started. The engineering gets us where we're going.

Want to bring agentic engineering into your business workflow? Book a free 30-minute call and let's figure out where AI agents can do the heavy lifting while your team stays in the driver's seat.

Sources: