Vibe Coding: The Shift from Syntax to Intent

Vibe coding moved the job from writing syntax to describing intent. Here is what that changed, what it quietly cost, and where the line sits for production work.

Vibe coding moved the job from writing syntax to describing intent. Andrej Karpathy named it in 2025, and within a year it had changed who gets to build software at all.

For the full plain-English explanation — what it is, where it fails, and what to do about it — read What Is Vibe Coding? This post is the shorter, more technical take.

Why syntax became an implementation detail

For most of my career, a large share of development time went to things that had nothing to do with the product: build configuration, boilerplate, dependency resolution, and the long tail of small syntax errors. Modern models handle that layer natively. You describe the component you want and get a working implementation using current standards.

That is a real shift, and it is why the term caught on so quickly. The bottleneck moved from typing to deciding.

The workflow

  1. Specify intent. Describe what you want in human terms — the behaviour, the constraints, the edge cases.
  2. Model execution. The AI writes complete components, applying current patterns without being told to.
  3. Supervision. Instead of debugging syntax, you review architecture: does this fit the system, and will it hold up?

What the speed hides

Step three is where vibe coding and professional practice part company. Karpathy’s original description involved not reading the code — giving in to the vibes. That is fine for a prototype. In production it produces a specific failure pattern: nothing crashes, the site looks correct, and something is quietly broken.

I have hit this on my own properties. A contact form that validated correctly and never delivered a message. An agent that replaced an entire working design rather than editing it. Neither announced itself.

Where the line sits

The distinction Karpathy drew in 2026 is the useful one. Vibe coding raises the floor — anyone can build something. Agentic engineering protects the ceiling — what gets built stays worth owning. Same models, same speed. The difference is a written spec, reviewed changes, tests, and a named human who is accountable.

The result is a step change in velocity: a solo founder can build hybrid systems that used to require a team and a quarter. That is worth having. It is only worth keeping if someone is reading the output.

More: What Is Vibe Coding? · Agentic engineering in depth · The Build Standard