What it means
Vibe coding is building software by describing what you want to an AI and accepting the code it writes, usually without reading it properly.
A vibe coder works more like a client than a programmer. They ask for a feature, run whatever comes back, and paste any error message into the chat for a fix. Plenty of professional developers lean on a large language model all day and still check every line. Vibe coders stop checking and judge the work only by whether it seems to do the job.
People split sharply over it. Fans love it for prototypes, personal tools and weekend projects, because an idea can become a working app in an afternoon. Experienced engineers tend to worry about what happens next. Code nobody has read can hide security holes, expose passwords or grow into a tangle nobody can maintain. An AI can also hallucinate a function or package that doesn’t exist, and a vibe coder may not notice until something breaks.
The phrase works as a verb too. You can vibe code a budgeting app, and the person who does it is a vibe coder. Depending on who’s talking, that’s a proud badge or a gentle put-down.
Where it came from
Unusually for slang, the coiner is known. AI researcher Andrej Karpathy used the phrase in a post on X in February 2025. He described a relaxed way of building small projects where he gave in to the vibes, accepted the AI’s changes without reading them and fed any errors straight back in. He presented it as fine for throwaway weekend projects, not as a way to build serious software.
That caveat got lost quickly. The phrase arrived just as AI coding tools had become good enough for non-programmers to build real apps, and those people needed a name for what they were doing. Within weeks it was all over developer forums, YouTube tutorials and tech news. Newer tools that act as AI agents, editing files and running commands on their own, made the habit even easier. By the end of 2025, vibe coding was turning up in dictionary word-of-the-year coverage.
It’s a neat case study in how slang spreads: a casual remark from someone with a big audience, landing in a gap in the language. The word “vibe” made a technical habit sound relaxed, a bit reckless and slightly funny.
| Vibe coding | Careful AI-assisted coding |
|---|---|
| You describe what you want and accept the result | You describe what you want and review the result |
| Errors get pasted straight back to the AI | Errors get read and understood |
| “It seems to work” counts as done | Done means tested and understood |
| Suits prototypes and personal tools | Needed for anything touching money or personal data |
How people actually use it
- “I vibe coded a little app to split our holiday costs.” Proud use from someone who can’t program.
- “This whole codebase is vibe coded and nobody knows how it works.” A complaint. The software runs, but nobody can safely change it.
- “Classic vibe coder, put the API key in a public repo.” Mockery of a security slip a careful developer would catch.
- “I’m not vibe coding, I read every change.” A defence from someone who uses AI but wants credit for checking its work.
- “Spent Sunday vibe coding and now I’ve got a weather dashboard nobody asked for.” Hobby use, close to what the phrase first described.
In a sentence
Mia: wait, you built that? you can’t code
Jordan: I can’t. I vibe coded it
Mia: so the AI built it
Jordan: the AI and my vibes, yes
Lead dev: who wrote the payment code?
Sam: technically nobody
Lead dev: please tell me it wasn’t vibe coded
Sam: it was a very confident vibe
Common mistakes
- Using it for all AI-assisted coding. Vibe coding specifically means not reading or understanding the code. A developer who uses AI but reviews everything is doing something else.
- Assuming vibe-coded software is always broken. The code can be perfectly fine. The problem is that nobody has checked, so nobody knows.
- Treating “vibe coder” as an insult every time. Plenty of founders and hobbyists use it about themselves with pride. Tone and context decide it.
- Thinking it means you can skip clear instructions. Good results still depend on describing what you want well, which is the heart of prompt engineering. Vibe coding is loose about the code, not about the request.
Related terms
- Prompt engineering: writing instructions for an AI carefully so it gives better results.
- AI agent: an AI tool that carries out multi-step tasks with little supervision.
- Hallucination: when an AI states something false with total confidence.
- No-code: building apps with drag-and-drop tools instead of code.
- Technical debt: the future cost of shortcuts taken in code today.
Questions people ask
Who coined the term vibe coding?
AI researcher Andrej Karpathy coined the term in a post on X in February 2025. He used it for building small projects by talking to an AI and accepting its changes without reading them.
Is vibe coding bad?
Vibe coding is fine for prototypes and personal tools, where a bug costs little. For software that handles payments, logins or personal data, skipping code review is a real security risk.
Can you vibe code without knowing how to program?
Yes, and that’s much of the appeal. People with no programming background build working apps this way, though they often get stuck when the AI can’t fix its own bug.
Why do engineers worry about vibe coding?
Code that nobody understands is hard to fix, extend or secure. Engineers worry about hidden bugs, leaked passwords and apps that fall apart under real use.
Is “vibe coder” an insult?
“Vibe coder” can be either a boast or a put-down. Hobbyists and founders often use it proudly, while experienced developers sometimes use it to suggest someone doesn’t understand their own software.
The short version
Vibe coding is building software by describing it to an AI and trusting whatever comes back. It’s brilliant for quick experiments and risky for anything serious. The term started with one post in early 2025 and spread because it named something lots of people were already doing.