Vibe coding is building by prompting an agent and steering on feel. You describe what you want, run whatever it produces, glance at the result, and prompt again. You accept the code without reading every line. The term is only half a joke: for a lot of work this is genuinely how people build now.
Where it shines
For throwaway work it is excellent. A quick script, a UI you are exploring, a prototype to test an idea: speed matters far more than craftsmanship, and vibe coding lets you cover ground in minutes that used to take an afternoon. If the code is going to be deleted next week, reading every line is wasted effort.
Where it bites
The risk is shipping code nobody understands. When you have not read it, you cannot reason about its edge cases, its security, or how it fails under load. Bugs hide in the parts you skimmed. And because a model sounds confident whether it is right or wrong, "it looked fine" is not evidence that it is fine.
- Great for prototypes, demos, and personal tools.
- Dangerous for anything with users, money, or data behind it.
- The line is production. Once code ships, someone has to actually understand it.
Related terms
Prototyping
Prototyping is using an agent to throw together a rough, disposable version of something fast, so you can see an idea working and decide what to actually build. You optimise for speed and learning, not polish, and you discard the result freely.
Read definition →Agent
An agent is a language model wrapped in a loop that lets it call tools, read the results, and decide what to do next. The model supplies the judgement; the loop and the tools give it hands.
Read definition →Human review
Human review is a person actually reading what an agent produced, understanding it, and taking responsibility for shipping it. It is the final quality gate that tests and automated review can support but never replace.
Read definition →