Vibe coding

Vibe coding without losing track of your system

Vibe coding is fast and fun until you cannot explain your own code. How to keep the speed and still know what you shipped.

Vibe coding is real, and it is fun. You describe what you want, the agent builds it, and you keep going. The cost shows up later: a bug in code you never read, in a design you never chose.

Keep the speed, keep the plot

You do not have to give up the speed to keep understanding. You need a few moments where you stop and look at what was decided:

• before a change that adds state, like a table, a cache or a queue
• after a change you could not explain to a friend
• before you ship anything that takes money or deletes data

Look, don't read

Reading every line kills the vibe. Looking at the few lines that matter does not.

deck is built for those moments. Ask your agent to show you, and it writes a short deck: a few sentences, each with the code it is about lit up beside it, and a small chart when the point is something that moves. You click through it in a minute, ask about whatever looks off, and keep going.

A lightweight loop

1. Build with your agent as usual.
2. At a natural stopping point, ask it to show you the decisions it made.
3. Push back on anything you would not have chosen.
4. Keep going, knowing what you shipped.