Vibe Coding
Writing software by describing what you want and accepting the result without reading it closely.
Vibe coding is letting the model write the code and judging it by whether it runs and roughly does the job. No reading the diff, no understanding the implementation, just a loop of describe, run, adjust.
It works surprisingly well for prototypes and throwaway scripts. It works badly for anything that has to survive: a security bug, a licence incompatibility, or a subtle logic error that only shows up at scale.
The honest framing is that vibe coding moves the work, it does not remove it. The time you skip reading is time you spend later debugging something you cannot explain. For a first draft it is a good trade; for production code it is a different bargain.
Related terms
Agent
A model with tools, a system prompt, and a loop that lets it act and observe results.
Code Review
A second pass by someone who did not write the code, looking for what the author missed.
Testing
The cheapest way to know a change is safe: a check that runs without a human reading anything.
Context Engineering
Deciding what goes into the model's context, and what stays out.
Human in the Loop
A person who reviews, approves, or corrects the agent's work at key points.
Want this working inside your team?
It starts with one conversation about your workflow.