Vibe Coding
Andrej Karpathy coined the term in a post on X on February 2, 2025: "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." In the same post he described talking to his coding assistant by voice and letting it write the code.
Vibe coding is a quick way to try an idea or build a personal tool. It becomes risky when the code handles money, personal data or other people's systems, because nobody has checked what it does. The usual next step is spec-driven development: write down what the software must do, then have an agent build and test against that spec. Agentic coding with tests and review is how a vibe-coded prototype becomes something you can ship.
Example
Build a single-page tool that splits a restaurant bill between friends, including the tip.
It should run in the browser with no server and no sign-in.
When you're done, tell me how to open it and list every assumption you made.When to use it
- Prototypes and demos you'll throw away
- Personal tools only you will use
- Exploring whether an idea is worth building properly
When not to use it
- Anything that stores personal data, takes payments or runs in production
- Code other people will have to maintain
- Security-sensitive work, where unread code is unreviewed code

