17
vibe coding
Drive a model to edit the repo in natural language. You review the diff, run the tests, name the move — syntax is not the first job.
What is vibe coding?
Vibe coding is a way of working: the human owns direction and acceptance, the model writes most of the code. It is not “you don’t need to know programming.” It moves what you know from syntax to spec, tests, and review.
Why does vibe coding matter when vibe coding?
The word gets used as an excuse. Smooth vibe coding looks like TDD, reverse engineering, slicing — with an agent on the keyboard. Unsmooth vibe coding is an unnamed wish and one generation.
How do you do vibe coding?
Each turn, name one move. Add constraints. Run tests. Read the diff. Do not spike and ship in the same turn.
How do you ask a model for vibe coding?
This is a vibe-coding turn. The move is (TDD / reverse engineering / a slice). Constraints below. Plan first, wait for OK, then edit. Run tests after.
What goes wrong with vibe coding?
Accepting “feels right.” A neighbouring implementation that feels right is exactly what the term was coined to avoid.