Describing the result, not the code
Vibe coding means conveying the feel of what you want to build in natural language and letting the AI handle the details of the code. The AI researcher Andrej Karpathy used the phrase in 2025 and it spread almost immediately, becoming one of the words of the year.
How it differs from writing code
Traditionally you learned the syntax and wrote line by line. In vibe coding you state what you want, try what comes back, and respond in words again — change this part. Not reading the details closely, and judging by whether it runs, is where the vibe comes from.
Agentic development tools such as Cursor and Claude Code are what made the style practical.
The upside and the risk
- Upside: prototyping is dramatically faster, non-engineers can build their own tools, and it is an effective way in for learners
- Risk: without understanding the code, you cannot see the security holes or the bugs. Production systems still need human review
Vibe coding for hobby work and prototypes, understanding and review for production code, is the sensible line as things stand.
Why it matters to non-engineers
The substance of vibe coding is the shift from programming as a specialist skill to something you can ask for in words. A budget tracker, a script that automates part of your job, a small game — it marks the point where wouldn’t it be nice if became something you can build yourself.
The phrase is used both approvingly and dismissively. The flip side of quick and easy is sloppy and fragile, so read for which sense is meant.
How fast the term spread says something about how fast development itself is changing.