Chapter Two · Vibe Coding and the Third Week
Vibe Coding and the Third Week
The antipattern the tool invites, and the loop that replaces it. Five topics define vibe coding precisely, take its honest uses seriously, follow Kai's 1,400-line waitlist from a green first week to a double offer nobody can trace, state the contract that accountability does not move to a tool, and lay out the six-stage loop the rest of the book teaches.
A coding agent makes one way of working very easy: describe what you want, accept what comes back, run it, and describe the next thing. It produces visible progress every few minutes, and on a weekend project it is a perfectly good way to work. On code that a team will change for three years, it produces something else, and the bill arrives later than the code does.
This chapter names that way of working and draws its boundary. It gives vibe coding a definition you can test against a single diff, accepting code you have not read, and separates it from simply using AI to write code. It takes the legitimate uses seriously and shows how to keep a throwaway thrown away. Then it follows Kai's waitlist at Cragmoor, built in one afternoon, through the week when two climbers were offered the same place and nobody could say why.
The last two topics turn the story into the book's position. Accountability for code stays with whoever merges it, so the author has to be able to answer for every line. And the way to keep the agent's speed without the third week is a loop of six stages, specify, context, generate, read, test, and commit or discard, which Chapters 3 to 9 teach one stage at a time.