# what-is-vibe-coding

# ai-lab-workshop-20251001

## plan

### **What is Vibe Coding?**

[Vibe coding](https://en.wikipedia.org/wiki/Vibe_coding) is a term initially coined by Andrej Karpathy in a Feb 2, 2025 tweet:

> 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. It's possible because the LLMs (e.g. Cursor Composer w Sonnet) are getting too good. Also I just talk to Composer with SuperWhisper 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. I "Accept All" always, I don't read the diffs anymore. When I get error messages I just copy paste them in with no comment, usually that fixes it. The code grows beyond my usual comprehension, I'd have to really read through it for a while. Sometimes the LLMs can't fix a bug so I just work around it or ask for random changes until it goes away. It's not too bad for throwaway weekend projects, but still quite amusing. I'm building a project or webapp, but it's not really coding - I just see stuff, say stuff, run stuff, and copy paste stuff, and it mostly works.

It resonated with a meme launched by another early 2025 tweet depicting Rick Rubin force pushing AI-generated code to the main branch of his repo


And Rick "Made the Meme Real" by writing a web-based book about Vibe Coding based on Laozi, [*The Way of Code: The Timeless Art of Vibe Coding*](https://www.thewayofcode.com/).

So why did this become such a thing? And is it worth learning? Can you even learn it if it doesn't involve any skill?

This is what we're going to explore today.

Further reading and viewing:

[The 15 Rules of Vibe Coding](https://medium.com/towards-agi/15-rules-of-vibe-coding-ive-learned-b3ae9eb3b4f2) is probably the article that first put the Rubin meme together with the vibe coding term on Feb 14, 2025.

Rubin then did some interviews to publicize the book which are highly watchable/listenable:

<iframe width="560" height="315" src="https://www.youtube.com/embed/6BDsFUvPqI0?si=ayb9wqX_juAI9Dp1" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>

and, if you can handle Andreessen

<iframe width="560" height="315" src="https://www.youtube.com/embed/7s9C92Pkcc0?si=ky3a2odv5S2-bOU9" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>

Once you get too excited about vibe coding it makes sense to check out the tweets and memes and articles that have been critical of it. Many document embarrassing fails by non-devs, like this ["5 Vibe Coding Failures That Prove AI Can't Replace Developers Yet"](https://www.finalroundai.com/blog/vibe-coding-failures-that-prove-ai-cant-replace-developers-yet).

This one is a favorite tale in two tweets:

#### 1

#### 2