Short answer: a researcher named Andrej Karpathy tweeted the phrase "vibe coding" on February 2, 2025, and it stuck. Eleven months later, Collins Dictionary named it Word of the Year 2026. That's the entire etymology. But the reason it stuck, that's the interesting part.
The tweet that named a movement
Karpathy is one of the most respected names in AI. He co-founded OpenAI, ran Tesla's Autopilot team, and his free deep-learning lectures are legendary. So when he tweets about how he builds software, people pay attention.
"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."
The tweet went on to describe how he was building little tools by talking to an AI, accepting whatever it produced, and iterating with feedback like "make it prettier" or "fix the bug at the top." No reading the code. No understanding the diff. Just vibes.
Why "vibe"?
The word "vibe" did a lot of work in that tweet. It captured three things at once:
- The feeling, not the syntax. You describe how you want the app to feel ("clean, minimal, fast") and the model handles the implementation.
- Trust the flow. You don't audit every line. You stay in a creative state and let the AI handle the mechanics.
- A little ironic, a little serious. "Vibe coding" sounds like a joke. It also describes exactly what's happening when someone builds a real app in an afternoon without writing a function.
From tweet to dictionary in 11 months
The phrase exploded for a reason: it named something millions of people were already doing but didn't have a word for. By mid-2025, tools like Lovable, Cursor, v0, Bolt.new, and Replit Agent had turned natural-language coding into a serious workflow. Founders were shipping startups. Designers were building prototypes. Marketers were spinning up landing pages overnight.
They needed a name. Karpathy gave them one.
In November 2026, Collins Dictionary made it official, naming "vibe coding" their Word of the Year 2026 and defining it as:
"The use of artificial intelligence, with prompts in natural language, to generate computer code, in which the user does not check or edit the code."
Is it just hype?
Some developers hate the term. It sounds frivolous. It implies you don't care about quality. And in fairness, the "don't read the code" framing is a real risk, if you ship something you don't understand, you can't debug it, secure it, or trust it.
But the name isn't really about not caring. It's about a shift in what you care about. Vibe coders care about the outcome: does the app work, does it look right, does it solve the problem? The AI handles the layer below that. It's not lazy, it's a different abstraction.
What to call yourself
If you build apps this way, you're a vibe coder. If you do it for work, you're a vibe coding founder, designer, or PM. The term is intentionally broad. It's not a job title, it's a description of how you build.
