Vibe coding

Vibe coding,
explained properly.

Vibe coding is building software by describing what you want in plain language and letting an AI write, run and revise the code — while you steer by looking at the result. Here is what it is, where it works, where it breaks, and twenty guides to get good at it.

Updated 2026-10-02 · 9 min read

vibe codingnoun · vibe · coding

A way of making software in which you describe the outcome in natural language, an AI model writes the code, and you judge the running result instead of reading every line.

Where it comes from

The phrase comes from Andrej Karpathy, who in February 2025 described a way of programming where you "fully give in to the vibes" — you talk to the model, accept its changes and steer by what you see, without reading every diff.

Within a year it named a whole category: browser builders that turn a sentence into a running app — Vantix, Lovable, Bolt, v0 — and AI-first editors such as Cursor that do the same inside a developer's codebase. The tools comparison covers how they differ.

01 DescribeSay what you want: who it is for, what it does, how it should feel.
02 GenerateThe model writes the files — components, styles, data, configuration.
03 RunThe app runs immediately, so you see the result rather than imagine it.
04 JudgeYou react to what is on screen, and the next prompt is your edit.
Six principles
  1. 1

    Outcome over syntax

    You describe behaviour and feel; the model handles the language features.

  2. 2

    The running app is the spec

    Arguments about requirements end when everyone can click the thing.

  3. 3

    Small steps, fast feedback

    One change per prompt. Big rewrites are where vibe-coded projects go wrong.

  4. 4

    You stay the editor

    The model proposes; you decide what stays. Taste is still a human job.

  5. 5

    Own the output

    If you cannot export it, you rented an app. Real code is the point.

  6. 6

    Know when to read the code

    Payments, permissions and personal data deserve a careful look — or a reviewer.

Where it works

  • Prototypes, MVPs and landing pages you need this week
  • Internal tools that replace a spreadsheet and three emails
  • Front-ends on top of APIs you already have
  • Turning a sketch or screenshot into a working screen
  • Letting non-developers try ideas before anyone writes a ticket

Where it breaks

  • Large, long-lived codebases nobody has read in months
  • Security-critical logic accepted without review
  • Vague prompts that ask for "an app like Airbnb"
  • Regulated data sent to a tool whose data path you never checked
  • Teams that skip version control because "the AI remembers"
Twenty guides

Get good at vibe coding

Try the loop yourself

Describe something small. Watch it run in under a minute.