What is Vibe Coding?

LessonBeginner10 min

What the term means and where it came from, how it differs from AI-assisted programming, and when it suits you.

10 minReading time
BeginnerLevel

In this lesson you will learn

  • The definition and origin of vibe coding
  • Telling it apart from AI-assisted programming
  • Knowing the limits of its use

Where the term came from

Andrej Karpathy coined the term "Vibe Coding" in a post on X in February 2025, describing it as a way of programming where you "fully give in to the vibes" and "forget that the code even exists", and said it suits throwaway weekend projects.

In this style you describe what you want in natural language, a language model or coding agent writes the code, and you try the result and ask for changes, without reading the code line by line.

How it differs from AI-assisted programming

Simon Willison draws a line between the two: vibe coding in the strict sense is building software with a language model without reviewing the code it writes. If you review, test and understand the code well enough to explain it to someone else, that is ordinary software engineering in which you used AI.

Today people use the term more broadly for any building driven by description and conversation. In this section we use it in the broad sense, and teach you when the "vibes" are enough and when you need review and testing.

When does it suit you?

  • Prototypes, quick experiments and testing ideas.
  • Small personal and internal tools.
  • Learning a new technology through a small project.

It needs more care when the app handles user data, payments or secrets, or when a team will maintain it for years. There, review and testing become indispensable.

Sources

  1. Andrej Karpathy's post that coined the term (February 2025)
  2. Simon Willison: Not all AI-assisted programming is vibe coding (19 March 2025)