What Is Vibe Coding
Vibe coding is a way of writing programs: you tell the AI what you want in natural language, the AI generates the code, you don't read the code, you only look at the results of running it, and if you're not satisfied you keep making requests. It was proposed by Andrej Karpathy (OpenAI co-founder, former head of Tesla's AI division) in early February (month 2) of 2025; in Chinese it's called atmosphere programming, and some also translate it as mood programming.
This section doesn't require installing anything—you can learn it all in the browser.
What You'll Be Able to Do After This Section
- Explain what vibe coding is in one sentence
- Judge whether an experience of "writing code with AI" counts as vibe coding
- State the scope of applicability its originator drew for it
It Came From a Tweet
Karpathy's original tweet is the source of this term. The gist in Chinese:
There's a new kind of coding I call "vibe coding": you fully give in to the vibes, embrace exponentials, and forget that the code even exists. It's possible because the LLMs (e.g. Cursor Composer with Sonnet) are getting too good. I also talk to Composer with SuperWhisper voice, so I barely even touch the keyboard. I ask for the dumbest things, like "decrease the padding on the sidebar by half," because I'm too lazy to find it myself.I just
Accept All, no longer read the diffs. When something goes wrong, I just copy-paste the error back in, without any explanation, and it usually fixes it.
If you can't open x.com, that's fine—all the key points are in the passage above.
What you should see: there are four actions in this passage. State requirements in plain language; AI writes the code; accept everything without looking at the changes; paste errors back verbatim. In the simulator on the guide page, these are exactly the four things you do.
- I can point out at least three "don't look at the code" practices from the tweet
The Most Important Line: Whether You Look at the Code
Many people call everything "writing code with AI" vibe coding. That's a misunderstanding. Engineer Simon Willison wrote a blog post specifically on March 19, 2025 (month 3) to correct it:
When I say vibe coding, I mean building software with LLMs without reviewing the code they write.
Conversely, he also made it clear: if the code was written by an LLM and you reviewed it, tested it thoroughly, and can explain to others how it works, then it's not vibe coding—it's software development.
So vibe coding is one kind of "AI-assisted programming," not a synonym for it:
| AI-assisted programming | vibe coding within it | |
|---|---|---|
| Does it use AI | Yes | Yes |
| Do you read the generated code | Read it, review and test it, can explain every line | Don't read it, accept everything |
| How do you judge good vs. bad | Code quality, security, maintainability | It runs and works, good enough |
| Suitable for | Formal products, team collaboration | Weekend side projects, prototypes, small tools for personal use |
Use two questions to confirm you can tell them apart.
Quiz timeYou had AI write a script, understood it, made two changes, and tested it yourself before using it. Does this count as vibe coding?
Quiz timeThe program threw an error, you pasted the error back into the chat as-is without adding a word, the AI fixed it and it runs now, so you call it done. Does that count?
- I can state the boundary line: whether you review, understand, and test the generated code
The Scope the Originator Drew
Karpathy wrote in the same tweet: it's still not bad for one-off weekend projects, and quite fun too. He also admitted that the AI doesn't necessarily understand the errors that come up or fix them well; sometimes you can only change random things until the problem goes away.
Willison added context: Karpathy is a very senior programmer, and he does this because the project risk is low—it's for speed and fun.
Remember this scope: small things for personal use, fine; things that handle money, handle secrets, or serve other people—can't rely on vibes alone. The reason is in the next section.
- I know what vibe coding is suitable for and what it isn't
How Fast It Blew Up
| Time | What Happened |
|---|---|
| 2023 | Karpathy said "the hottest new programming language is English" |
| Early February (month 2) of 2025 | Karpathy tweets and proposes vibe coding |
| 2025-02-27 | New York Times reporter Kevin Roose (not a professional programmer) tries it hands-on and builds several small apps |
| 2025-03-06 | Y Combinator says that in the 2025 winter batch, 25% of startups had more than 95% of their code generated by AI |
| 2025-03-08 | Merriam-Webster adds it to "Slang & Trending" |
| 2025-03-19 | Simon Willison publishes a post drawing the line between it and AI-assisted programming |
| 2025-06-04 | Andrew Ng criticizes the name as misleading, making people think developing with AI is just "going with your gut" |
| 2025-11-06 | Collins English Dictionary names it Word of the Year |
| January (month 1) of 2026 | Linus Torvalds uses it to build a visualization tool for his AudioNoise project |
One thing to note when reading this table: YC's "25% / 95%" is a single data point from March (month 3) of 2025, and cannot be extrapolated to "all code today is written by AI."
Checkpoint
- I can explain vibe coding in one sentence: using natural language to have AI write code, without reading or reviewing it, and iterating based on the results of running it
- I know the person who coined it is Karpathy, in early February (month 2) of 2025, and that it's called atmosphere programming in Chinese
- I can state the dividing line between it and AI-assisted programming
- I know its applicable scope: fine for weekend side projects, but a production product can't rely on it alone
Common misconceptions
Treating Karpathy's tweet as a "call for everyone to stop reading code." He was talking about weekend side projects. Applying this practice to systems that handle money, manage secrets, or serve other users is the source of the incidents in the next section.
Thinking vibe coding is a specific tool. It is a practice. Many tools can be used this way; the one in Karpathy's tweet was Cursor Composer. This course covers four: Claude Code, Codex, OpenCode, and WorkBuddy, compared in 1.4. For other terms you don't understand, check the glossary.
FAQ
What does vibe coding mean?
It is a way of writing programs: you tell the AI what you want in natural language, the AI generates the code, you don't read the code and only look at the running results, and if you're not satisfied you keep making requests. The term was coined by Andrej Karpathy in early February (month 2) of 2025, in one of his tweets.
What does atmosphere programming mean?
Atmosphere programming is the Chinese translation of vibe coding; some also translate it as mood programming. It refers to the practice of building software with an LLM without reviewing the code it writes. It is one form of "AI-assisted programming," not a synonym for it.
What's the difference between vibecoding and ordinary AI-assisted programming?
The dividing line is whether you read the code. Vibe coding means not reading the generated code, accepting all of it, and only caring that it runs; if you review the code, test it thoroughly, and can explain to others how it works, then it's software development, not vibe coding. This distinction was explicitly drawn by engineer Simon Willison in a blog post on March 19, 2025 (month 3).
Where is vibe coding appropriate?
Karpathy, who coined the term, drew the scope himself: one-off weekend projects, prototypes, small tools for personal use. Things that handle money, manage secrets, or serve other users can't rely on vibes alone, because the AI may not understand the errors that appear, and may not fix them well.
Next section
Some people have used it to build a small shippable product in a week, while others say everything it writes is full of problems. 1.2 Is it reliable: risks and truth looks at what research data and real failure cases say.