AI CompendiumA public chart of the language
Home / Patterns of Work / Vibe Coding
Patterns of Work

Vibe Coding

Building by prompt-and-accept, without reading the code.

Definition

Writing software by describing what you want and accepting generated code without close inspection. Fast and excellent for throwaway prototypes; genuinely risky for anything maintained.

The term names a real continuum. The honest version is fine for a spike you will delete; applied to production code that others must maintain, it pushes the cost downstream.

The right posture is not prohibition but scoping: name which parts of the codebase are allowed to be generated without close reading. Prototypes, internal scripts and throwaway analyses are legitimate. Anything with users, data or a maintenance horizon is not, because the cost of unread code lands later and on somebody else.

How people use it
Justifying a weekend prototype.
"It is a vibe-coded prototype, it dies on Monday. But it proves the interaction works before we build it properly."
Worked example

The prototype that became load-bearing

A weekend tool built by prompt-and-accept is now used by a team daily.

There is no test, no error handling, and nobody knows what it does on an unexpected input. The honest options are to harden it deliberately or to declare it disposable and reimplement. The failure is the middle path, where it is neither.

Avoid

Using the label to skip review on code that will be maintained. The bill arrives as debugging.

Sources
Related terms