What is Vibe coding?
Vibe coding is the practice of producing working software by describing the intent or aesthetic ("the vibe") in natural language to an AI assistant that fills in the implementation. Iteration is conversational rather than compile-edit-run. The work-product still has to satisfy a specification, but the specification lives in plain English and the developer's job shifts from writing syntax to judging output.
Also known as: vibe-coding, prompt-driven coding, intent coding, natural-language programming
Origin of the term
"Vibe coding" emerged informally in early 2025 as developers noticed they were shipping useful code without consciously thinking in syntax. The term was popularized by AI-tool builders demonstrating prompt-to-app loops on stage — "I'm just vibing with the AI" — and stuck because it captured the felt experience of the new workflow. By 2026 it was the industry's working term for the prompt-first software-building paradigm.
What you actually do when you vibe-code
Open an AI app builder (Mira Code, Lovable, Bolt.new, v0). Describe the app: "a markdown notes app with dark mode, sidebar of files, autosave, deploy to Vercel." The AI generates the React/Tailwind project. A live preview renders in your browser. You see what's wrong ("the sidebar is too wide", "dark mode breaks on the editor view") and prompt fixes. Iterate. The compile-edit-run loop is replaced by describe-see-redirect.
Why it works in 2026 specifically
Three things crossed thresholds together: (1) LLMs got reliably good at generating coherent multi-file React/Tailwind code, not just snippets. (2) In-browser sandboxes (WebContainer, NodePod) got fast enough that a generated app boots in seconds, not minutes. (3) Live-preview frameworks streamlined the see-redirect loop so feedback is immediate. Below all three, the underlying models reached a level where the success rate on "build me a useful single-page app from five sentences" went from occasionally surprising to boringly reliable.
What vibe coding is good and bad for
Good for: prototypes, internal tools, single-page apps with clear scope, demos, learning by example, the layer between "idea" and "production engineering". Bad for: high-scale production backends, anything with non-trivial security or compliance requirements that a non-engineer can't validate, novel algorithms that the model doesn't have in its training distribution, codebases where the model can't see enough context to reason about side effects. Treat it the same way you'd treat a junior engineer's PR: reviewable, useful, not infallible.
The skill that replaces typing
Vibe coding doesn't make programming skill obsolete — it shifts which skills matter. The high-leverage skills become: writing clear specs, reading generated code critically, knowing when to step in and edit by hand vs prompting again, structuring projects into pieces the model can reason about in one context, and recognizing security or performance issues the model produced. People who already had those skills get faster; people who lacked them have to develop them to ship reliable work.