Who Coined Vibe Coding?

Andrej Karpathy coined the term vibe coding. He introduced it on February 2, 2025, in a short post on X (formerly Twitter). Karpathy is a founding member of OpenAI and the former director of AI at Tesla, so when he described a new way of building software, people paid attention. His exact words were: "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." He added that it works because large language models like Cursor Composer with Claude Sonnet were getting good enough that he barely had to touch the code himself. That single post, which he later called a throwaway "shower thoughts" tweet, named a movement.

I am Mahmoud Zalt, an independent senior AI systems architect with 16 years building production software since 2010. I am the founder of Sista AI, where I run a workforce of autonomous AI agents in production, so I have watched this shift happen from the inside rather than from the sidelines. I wrote this because the origin of vibe coding gets garbled constantly online, and getting the facts right actually matters for understanding what the term does and does not mean.

The Exact Post That Started It

Here is the full text of Karpathy's original February 2, 2025 post, so you have it verbatim:

• "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."

He went on to describe the actual workflow: asking the AI for changes, accepting almost everything it wrote without reading the diffs closely, pasting in error messages, and letting the model fix its own mistakes. When something broke that the model could not solve, he would just work around it or ask for a random change until the problem went away. That casual, results-over-review attitude is the heart of what he meant. It was never presented as a rigorous engineering discipline. It was Karpathy describing how he throws together weekend projects when he does not care about the code, only the outcome.

When Did Vibe Coding Start, and Why Is It Called That?

Vibe coding started on February 2, 2025. That is the date of Karpathy's post. The practice it describes, prompting an AI to write code for you, existed before the name did, but the phrase gave scattered behavior a single memorable label, which is usually when a trend becomes a movement.

Why is it called vibe coding? The name comes straight from Karpathy's phrase "fully give in to the vibes." The idea is that you stop thinking like a traditional programmer who reads and controls every line, and instead you steer by feel: describe what you want, glance at whether the result feels right, and keep nudging the AI until it does. You are coding by vibes rather than by careful line-by-line authorship. The word "vibe" captures the loose, intuitive, trust-the-output nature of it. It is deliberately not a serious engineering term, which is part of why it spread so fast and also why it later caused so much argument.

A Short History: From Tweet to Word of the Year

The speed at which this term traveled is genuinely remarkable. Here is the timeline from a throwaway post to a dictionary entry:

What is worth noticing is how the meaning drifted. Karpathy used vibe coding to mean a specific, casual style: accept the AI output, do not read it, iterate by feel. Within months, the phrase got stretched to cover all AI-assisted development, including careful professional work where engineers review everything. Those are very different activities, and conflating them is the source of most of the online fights about whether vibe coding is good or dangerous.

What Karpathy Actually Meant vs How People Use It

If you want to sound informed about the origin, this distinction is the whole game. There are effectively two definitions in circulation:

My honest take, having shipped AI-built systems into production: Karpathy's original version is a fantastic way to prototype and a terrible way to ship anything real. The vibes are perfect for exploring an idea in an afternoon. The moment other people depend on the software, or money moves through it, you need the discipline that vibe coding explicitly throws away: reading the code, testing it, hardening it, and understanding what it does. The name is catchy, but the practice has a ceiling, and knowing where that ceiling is separates people who build toys from people who build products.

Where the Vibes Stop and Real Building Begins

Understanding the origin is fun trivia, but the useful question is: how do you take the energy of vibe coding and turn it into something that actually works and lasts? That is the exact gap I wrote The Vibecoder's Handbook to close. It respects the speed and joy of building by feel, then shows you the steps that stop your project from collapsing the moment it meets a real user.

The short version of my method: use vibe coding to plan and prototype fast, then deliberately shift gears. Set up your project properly, build in reviewable chunks, and add the checks that Karpathy's original definition skips. You do not have to become a traditional software engineer to do this. You just have to know which corners are safe to cut and which ones will cut you back. If you want a hand applying this to something real, that is exactly what my AI consulting practice is for.

Frequently Asked Questions

Who coined the term vibe coding?

Andrej Karpathy coined vibe coding. He is a founding member of OpenAI and the former director of AI at Tesla. He introduced the term in a post on X on February 2, 2025.

When was vibe coding invented or coined?

The term was coined on February 2, 2025. The practice of prompting AI to write code existed earlier, but Karpathy's post on that date is what named it and made it spread.

What was the original vibe coding quote?

Karpathy wrote: "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."

Why is it called vibe coding?

It is called vibe coding because of Karpathy's phrase "fully give in to the vibes." Instead of reading and controlling every line of code, you steer the AI by feel and intuition, judging the result rather than authoring it directly.

Did Andrej Karpathy invent vibe coding as a serious method?

No. Karpathy later called it a throwaway "shower thoughts" tweet. He described a casual style for low-stakes weekend projects where you do not review the code, not a rigorous engineering discipline for production software.

Is vibe coding officially recognized?

Yes. Merriam-Webster listed it as a slang and trending term in March 2025, and Collins English Dictionary named vibe coding its Word of the Year for 2025.

The Origin in One Line, and What to Do With It

Vibe coding was coined by Andrej Karpathy on February 2, 2025, in a casual post on X that described building software by feel and letting AI write the code. It went from a throwaway tweet to Collins Dictionary's Word of the Year in under a year. That is the whole origin story. The more interesting story is what you build next.

If Karpathy's idea got you excited to build, the natural next step is learning how to take that energy past the prototype stage into something real and durable. That is what my free book is for. It is free through the Plan, Set Up, and Build chapters, with advanced Harden, Ship, Operate, and Scale material for when you are ready. Read the free handbook ->