Vibe coding basics

Vibe coding vs AI-assisted development: where is the line?

Published Updated 8 min read

Read in : Français

Contents
  1. Where exactly is the line?
  2. It's not binary: a five-level spectrum
  3. Vibe coding vs AI-assisted development: side by side
  4. When is pure vibe coding good enough?
  5. What do the numbers say about each approach?
  6. How do you move from vibe coding to AI-assisted development?
  7. Is the line blurring in 2026?
  8. Frequently asked questions
  9. Frequently asked questions
  10. Sources

The line between vibe coding and AI-assisted development isn't about the tool, it's about what you do with the code: if you review it, understand it and test it before you rely on it, you're doing AI-assisted development; if you only judge by the result, you're vibe coding. Both use the same tools and the same models. What changes is the level of risk, and therefore the kind of project you can take on without getting burned.

Where exactly is the line?

The line is code review: vibe coding means building software with an AI without reviewing the code it writes. That's the definition from developer Simon Willison, who wrote the go-to piece on the subject back in March 2025.

If an LLM wrote the code for you, and you then reviewed it, tested it thoroughly and made sure you could explain how it works to someone else that's not vibe coding, it's software development.

— Simon Willison, simonwillison.net

His golden rule for production code: he won't commit any code he couldn't explain exactly to somebody else. Google Cloud draws the same distinction, separating "pure" vibe coding, where you trust the AI's output, from "responsible AI-assisted development," where the user reviews, tests and understands the code and takes full ownership of the result.

Keep three criteria in mind:

  1. Review: has anyone read the code?
  2. Understanding: can anyone explain what it does?
  3. Verification: do tests prove it does what it should?

If the answer is no to all three, it's vibe coding. For the history of the term and its other meanings, read what vibe coding means and where it came from.

It's not binary: a five-level spectrum

Between "I never look at the code" and "I review every line," there's a whole range of practices. Addy Osmani, an engineering leader at Google, describes a spectrum running from vibe coding to AI-assisted engineering, through more planning and spec-driven development. Here's a practical way to slice it:

LevelWhat you doTypical example
0. Pure vibe codingYou prompt, accept everything, judge by the screenA mini game for your kids, a throwaway prototype
1. Scoped vibe codingYou write a spec and move in small steps, without reading the codeAn internal tool for your team, no sensitive data
2. Verified vibe codingYou add tests and a security checklist, and save every versionAn MVP shown to early customers
3. Spec-driven developmentThe agent follows a written spec, you review the sensitive partsA SaaS with user accounts and payments
4. AI-assisted developmentA human reviews, understands and approves every changeA production app maintained by a team

Level 3 has a name: spec-driven development, pushed in particular by GitHub's open-source Spec Kit. The scoping at level 1 is covered in writing a PRD your AI builder understands.

Vibe coding vs AI-assisted development: side by side

The two practices differ less in their tools than in their process and who takes responsibility.

CriterionVibe codingAI-assisted development
Code reviewNone, or almost noneSystematic, at least on sensitive parts
Starting pointAn idea, a promptA design, a specification
Testing"I clicked around, it works"Automated tests and security checks
Who decidesThe AI proposes and appliesThe AI proposes, a human approves
Typical toolsBrowser-based app buildersCode editors and agents, usually with Git
Speed at the startVery fastSlower, but steadier later
Main riskInvisible flaws and bugsTime spent reviewing
Good fitPrototypes, personal tools, demosApps with users, data or money

Watch out for the tool trap: you can vibe code in Cursor or Claude Code by accepting everything unread, and do serious development in Lovable by opening the code and testing every step. The tool makes one practice easier; it doesn't decide it for you.

When is pure vibe coding good enough?

Pure vibe coding is good enough when a mistake costs almost nothing and you're the only one who pays for it. Andrej Karpathy, who coined the term, kept it for "throwaway weekend projects."

Use this decision tree:

What do the numbers say about each approach?

Published research shows professionals are cautious about vibe coding, and that even with review, AI guarantees neither speed nor security.

The lesson: AI-assisted development isn't "vibe coding with more effort." It's a practice where review and testing are the core of the work.

How do you move from vibe coding to AI-assisted development?

You make the move by adding guardrails one at a time, without having to become a programmer overnight. Here are six steps, in order of payoff.

  1. Write the spec before the code. Addy Osmani recommends starting from a solid design and having the AI help write the spec before generating code.
  2. Save every version that works. With Git you can always roll back: Git for vibe coders.
  3. Give the AI a way to check its own work. The Claude Code docs are clear: ask the agent for evidence, the command it ran and its output, rather than a bare "all tests pass."
  4. Have tests written. Osmani suggests having the AI generate or run tests and security checks on every new feature. Testing AI-generated code when you're not a developer shows you how.
  5. Keep the final say. The AI proposes changes, a human approves them. At the very least, read the summary of each change.
  6. Get the sensitive areas reviewed. Authentication, payments, data access: that's where human review pays off most.

Here's a prompt you can paste to make your agent work this way:

Before changing any code, explain in 5 lines or fewer what you will change and why.
After the change:
1. List the files you modified.
2. Write or update a test that checks the new behavior.
3. Run the tests and show me the command and its output.
4. Flag anything that touches authentication, payments or user data.

Is the line blurring in 2026?

Yes, and it's the trend to watch. In February 2026, Andrej Karpathy said he preferred the term "agentic engineering" for professional work with coding agents, because there is "an art & science and expertise to it." The word "engineering" stresses rigor, not vibes.

In May 2026, Simon Willison admitted the two practices had started to blur in his own work: as agents got more reliable, he stopped reviewing every line, even for production code. He compares it to trusting another team's service through its documentation, while flagging the catch: a coding agent has no professional reputation to protect.

For you, the consequence is practical. If you don't review everything, your tests, your spec and your security checklist become your real review. To pick tools suited to this way of working, see Cursor vs Claude Code vs Codex, and for the big picture, the complete vibe coding guide.

Frequently asked questions

Frequently asked questions

Is vibe coding the same as AI-assisted development?

No, not in the strict sense. Vibe coding means using an AI to write code without reviewing what it produces, judging only by the result. AI-assisted development uses the same tools, but a human reviews, understands and tests the code before relying on it. The difference lies in the process and in who takes responsibility, not in the tool.

Can professional developers vibe code?

Yes, and many do for prototypes, one-off scripts or personal tools. Andrej Karpathy, a highly experienced programmer, coined the term while describing his own approach to throwaway projects. What sets a professional apart is knowing when to stop vibe coding and switch to review and testing.

Do you need to know how to code for AI-assisted development?

You need, at minimum, to be able to read code and understand what it does, or to work with someone who can. You don't have to write every line, but you must be able to check that a change does what it claims. Automated tests and a written spec help, without replacing review on the sensitive parts.

Which tools are best for AI-assisted development?

AI code editors like Cursor, command-line agents like Claude Code or Codex, and GitHub Copilot are the most common, because they show you every change and integrate with Git. Browser-based app builders can work too, as long as you open the code, review it and test it.

Does my vibe-coded prototype need a rewrite for production?

Not necessarily a rewrite, but it does need hardening. Addy Osmani recommends treating a vibe-coded prototype as disposable or as scaffolding, and hardening it before production: review the sensitive parts, add tests, check security and access rules. Sometimes starting over from a clean spec is cheaper than patching.

Sources