Skip to main content
Vibe Code Forum

Article: What is vibe coding? A plain-English introduction

Vibe coding means building software by describing what you want in plain language and letting an AI tool write the code. You look at the result, say what to change, and repeat until it works.

The name comes from a post by AI researcher Andrej Karpathy in early 2025, describing a way of working where you "give in to the vibes" and stop reading every line of code. It stuck, and now covers a wide range of ways of building with AI.

What it looks like in practice

You type something like:

Make a page where I can add the books I've read, with a star rating, and keep them when I refresh the page.

A minute later you have a working page. You try it, notice the stars are too small, and type "make the stars bigger and show the newest book first". That loop of ask, look, adjust is vibe coding.

What it is good for

  • Personal tools: trackers, calculators, dashboards, small websites.
  • Prototypes: showing an idea to customers or investors before paying a developer.
  • Automating boring work: turning spreadsheets into reports, moving data between apps.
  • Learning: many people learn real programming by reading what the AI wrote.

Where it gets hard

AI tools are confident even when they are wrong. The difficult parts are not writing code, they are:

  • Knowing what you want precisely enough to describe it.
  • Checking it works, including the cases you didn't think of.
  • Keeping secrets safe: API keys and user data.
  • Not breaking what already works when you ask for the next change.
  • Running it for real: hosting, costs, backups, updates.

None of these need you to become a programmer, but they do need you to understand a handful of ideas. That is what this forum is for.

Vibe coding or "AI-assisted coding"?

Some people use "vibe coding" only for the hands-off style where you never read the code, and "AI-assisted coding" when you review everything. In practice most people slide between the two. Start hands-off, and read more of the code as your project starts to matter.

Next: Which path should you take?

Read next: Which path should you take? Choosing your way in and Prompting that works: small steps, clear checks.

More in Start here