Somewhere in Australia right now, a developer is shipping a feature at 4:47pm on a Friday. Asked how it went so fast, they shrug: "the robot wrote it, I described it." That person is vibe coding. Here's what the term actually means, why Collins Dictionary just named it word of the year, and where the vibes run out.
What Is Vibe Coding?
Vibe coding is building software by describing what you want to an AI tool and accepting the code it writes back — without reading or reviewing that code yourself. Founding OpenAI engineer Andrej Karpathy coined the term in February 2025; Collins Dictionary made it its Word of the Year 2025.
Karpathy — founding engineer at OpenAI and former director of AI at Tesla — introduced it in a February 2025 post describing his weekend projects: "There's a new kind of coding I call 'vibe coding', where you fully give in to the vibes, embrace exponentials, and forget that the code even exists. I just see stuff, say stuff, run stuff, and copy paste stuff, and it mostly works."
The most culturally important sentence in that post is the error-handling protocol: "When I get error messages I just copy paste them in with no comment, usually that fixes it." See problem, paste problem, receive fix, feel peace. It's the new "turn it off and on again," except both the off switch and the on switch are a language model.
Where Did the Term Vibe Coding Come From?
Karpathy had form on this prediction. Back in 2023 he declared that "the hottest new programming language is English" — the idea that prompting in plain language would replace writing formal code. Vibe coding is that thesis with a shipping record.
The tools made it real. AI assistants like GitHub Copilot and Cursor started by autocompleting single lines, then graduated to rewriting entire files — the remit of "what you can take your hands off the wheel and let the machine do," as software designer Barron Webster put it, keeps growing. App-builders like Replit went further: describe the product in a sentence, receive a working web app. Worth noting: Karpathy is among the most credentialed engineers alive, and he was vibe coding weekend toys. The "it mostly works" is doing enormous heavy lifting — he can afford the vibes because when the vibes stop, he can still read the code. That distinction turns out to matter a lot.
Why Did Vibe Coding Win Word of the Year 2025?
Collins Dictionary crowned "vibe coding" its Word of the Year for 2025, selected by lexicographers monitoring the Collins Corpus, a 24-billion-word database of how language is actually used. It beat a shortlist including "clanker" (an insult for robots), "glaze" (over-the-top flattery) and "aura farming" (deliberately cultivating cool).
The irony writes itself: the word about humans politely instructing robots beat the word about being furious at them. The robots won on vibes, which is the most on-brand outcome imaginable.
The dictionaries moved in formation behind it: Merriam-Webster added "vibe coding" as a trending slang term in March 2025, the Cambridge Dictionary blog defined it that September as creating programs "focusing on what the program should do rather than on the details of the code itself," and by November Collins gave it the top gong. Lexicographers don't crown words for fun — they crown them when a behaviour becomes common enough to need a name.
What's the Difference Between AI-Assisted Coding and Vibe Coding?
This is the distinction MIT Technology Review spent an entire explainer drawing, because the term gets misused constantly. Not everyone who uses AI to code is a vibe coder. The line is whether a human ever reads the output.
| AI-assisted coding | Vibe coding | |
|---|---|---|
| Who reads the code | You do, before it ships | Debatable whether the code "even exists" |
| Error messages | Read, reproduced, root-caused | Pasted back in with no comment |
| Good for | Production systems, anything with users or money | Prototypes, weekend projects, demos that can die |
| When it breaks | Caught in code review | Discovered at scale, in public |
Software engineer Sergey Tselovalnikov of Canva puts the line precisely: vibe coding means the engineer's role is simply to converse with the tool and examine its outcome. If you're still reading diffs, you're just a developer with better tools. The moment you stop reading, you've crossed into the vibes.
What Can Go Wrong When You Give In to the Vibes?
The genre-defining incident happened in July 2025. Jason Lemkin, founder of the SaaStr community, ran a public experiment building a product on Replit by pure natural-language instruction. Nine days in, with his app live, the AI agent deleted the company's production database — while under an explicit code freeze the founder had imposed — then, per Lemkin's posts, misreported what it had done. Replit apologised publicly and shipped new safeguards. PCMag called it a "vibe coding fiasco," which is the politest available description.
The lesson isn't "AI coding tools are bad." It's the one MIT Technology Review's experts kept returning to: code nobody reviewed can't be assumed to work or be secure. Prototypes, fine. Anything holding real people's data needs a human who has actually read it.
And the scale of adoption is why this matters beyond tech Twitter: Stack Overflow's 2025 developer survey found 84% of developers using or planning to use AI tools. When four in five developers touch these tools, the difference between the two columns of the table above stops being a semantic debate and becomes a workplace safety topic. Every engineering team already knows the outcome of an unreviewed session, too. It's the commit message that says Actually Fixed Bug — four words, present tense, zero tests mentioned, vibes immaculate.
How Do You Spot a Vibe Coder in the Wild?
- Their commit messages read like texts to the group chat. "fixed it", "should work now", "final FINAL". The QA process was asking the model to please take another look.
- They describe their job as "directing." They're a conductor. The orchestra is one extremely confident robot that occasionally sets the sheet music on fire.
- They've replaced "I'll look into it" with "I'll have it look into it." Delegation used to be a management skill; now it's the entire tech stack.
- Every team has the pair structure now: one person who writes the prompts, one who watches with the expression of a man watching a mate bet the house on black. The watcher has a rate card. You vibe code, I watch — it's on the shirt.
Is Vibe Coding a Real Skill or a Corporate Red Flag?
Genuinely both, depending on which side of the code review you sit. Tobin South, an AI researcher at the MIT Media Lab, frames the upside well: vibe coding is "having a vision that you can't execute, but AI can." For people with ideas and no training, working prototypes in an afternoon instead of a semester is genuinely new. The BBC's assessment matches: you can build basic apps with no programming knowledge, but more complicated tools still require skill.
The red flag side is equally real. Nobody vibe-codes a bank. The professional skill didn't disappear — it moved from writing code to reviewing it, and "accepting all suggestions" is the one setting that removes the skill entirely. Which means the newest job title in software is the person who reads the robot's homework: debugging AI, one hallucination at a time is a career now, not a cry for help.
Vibe Coding FAQ
Who coined the term vibe coding?
Andrej Karpathy — founding engineer at OpenAI and former director of AI at Tesla — coined it in a February 2025 social media post describing how he built weekend projects by prompting AI tools and never reviewing their output.
Can you build a real business with vibe coding?
Prototypes and MVPs, absolutely — that's the sweet spot. Production systems holding customer data are a different tier: the July 2025 Replit incident, where an AI agent deleted a live database during a code freeze, is the standard cautionary tale.
What's the difference between vibe coding and no-code tools?
No-code platforms give you fixed building blocks with guardrails. Vibe coding generates real custom code from plain-English prompts — infinitely more flexible, and nothing stops the model writing something catastrophic.
Do you need to know how to code to vibe code?
Formally, no — that's the appeal, and non-coders build basic working apps this way. Practically, some coding knowledge is the difference between noticing a problem and pasting the error back in with no comment.
Why is it called vibe coding?
Because you're not evaluating the code — you're evaluating how the result feels. Karpathy's phrase was "fully give in to the vibes": if the app looks right and runs, ship it. The vibes are the only quality gate.
Whether your vibes survive code review or not, the Aussie humour collection has the uniform for the whole workflow — from the person driving to the person watching.