EraCode glossary
Vibe coding
Definition
Vibe coding is a colloquial term for development driven by intuition and AI prompting rather than deliberate reading and reasoning about code — popularized to describe lightweight, prompt-first workflows.Also called: prompt-driven coding, intuitive AI coding
The phrase is honest about how a lot of AI-assisted work actually feels. The risk is when "vibe" becomes the whole workflow and the supervision step quietly disappears.
What it looks like in practice
Vibe coding tends to be conversational: the developer describes intent, accepts a draft, iterates by feel, and ships when the result looks plausible.
It works well for prototypes, throwaway scripts, and exploration. It works less well when correctness matters, the codebase is unfamiliar, or the change has to survive review and maintenance.
What causes problems
The risk is not vibe per se. The risk is the absence of the steps that catch bad output: reading the diff, predicting behavior, running the code, and debugging from a real failure.
When those steps are skipped repeatedly, the developer loses the practice that lets them tell good vibes from bad ones — and quality follows.
How to keep it honest
Use vibe coding where it fits. Outside those cases, keep a workflow that includes reading, running, and debugging the code the assistant produced.
EraCode supports that supervision loop with short, stack-aware practice that keeps debugging and code-reading instincts sharp even when the day-job mostly looks like prompting.