vibe coding

Vibe coding is fast.
Then the bill comes.

Describe what you want. Take back whatever the model gives you. It feels like magic for a weekend. It falls apart the first time the work has to stand up in front of users, a team, or production.

See what comes next →
what it is

What is vibe coding?

Vibe coding is when you describe what you want to an AI and ship whatever it hands back. No spec, no plan, no check that the output matches the ask. It is fast, and for a throwaway prototype that is fine. The bill arrives later. Packages the model made up. Bugs that pass a glance and break in production. Code nobody on the team can explain.

Say the vibe. Ship the guess.

why it breaks

It looks right. That is the trap.

invented pieces
APIs and packages it leaned on that were never real. The code imports something that does not exist, and you find out at runtime.
quiet bugs
Mistakes that pass a glance and surface later, in production, on a Friday.
looks right, isn't
Code that reads clean and does not do what you asked. The hardest kind to catch, because nothing looks wrong.
debt on the clock
Speed today, paid back later as fragility and rework. You borrowed against a future sprint, and the interest is real.
what actually happened

The plan didn't get faster. It got skipped.

Software used to answer to a plan. The requirements, the design, what "done" meant. AI let us jump straight to the output and leave the plan behind. The gap where it stood is still there, holding nothing up.

the honest scorecard

Fast, or provable. Until now.

  the old way vibe coding CRAFT
Speed Slow Fast Fast
Can you prove it? Yes No Yes
"Why is it like this?" There's an answer Nobody knows There's an answer
What breaks Your timeline Production Nothing silent

A river runs fast because it has banks. Take them away and you get a swamp.

what comes next

Keep the speed. Lose the faith.

Anti-vibe coding is not a return to the slow way. It puts the plan back as a spec you can audit, and checks every step against it. You still move fast. You just stop shipping on faith. That discipline has a shape, and the shape is CRAFT.

The discipline
Why anti-vibe coding exists, and what it refuses. Anti-vibe coding →
The pipeline
The five stages that make AI-built software provable. The CRAFT pipeline →
The checks
Three checks on every step, none of them trusting the last. How it works →
your next step

Seen enough? Prove it on your own work.

The live check runs in your browser and returns a verdict in seconds. When you want it on the real thing, send one piece of work. A person reads it, runs it with you, and shows you the pass.

See it check your own work → Request access →

nothing uploaded · nothing to pay for the first run · a person reads every note