An afternoon that used to be a week is real, and so is the small change three weeks later that costs four days. This chapter reads both halves honestly: what a coding assistant is, why vibe coding genuinely works, what the unread pile invoices, and the four habits that keep the speed without the bill. It ends by taking the agentic tool apart in this book's own vocabulary — the same request, in a loop, with exactly one new step.
Tessa writes no code and this chapter will not change that. It is here because she is about to commission a small piece of software, sit opposite agencies whose timelines assume these tools, and hear the sentence "AI wrote it" used as reassurance in one meeting and as an accusation in the next. Judging all three is a skill, and it is a skill this book has almost finished teaching without mentioning code at all.
Five pages, and they run as an argument. What a coding assistant actually is — the same model from Chapter 1, pointed at a genre of text it happens to be very good at, on three rungs of tooling that outlast the products standing on them. Then vibe coding, taken seriously: an afternoon that used to be a week, and it genuinely works. Then the third week, when the demo becomes a product and a small change costs four days — a bill that traces, precisely, to three disciplines nobody kept. Then the version of the same work that keeps the afternoon and skips the bill, built out of four habits the reader has been practising on prose since Chapter 3. And last, with the analogies retired, the plain answer to what an agentic tool is: this book's request, in a loop, with one step in it that is new.
The same page, two weeks apart
Week one
Describe it, watch it build, click around, describe the next change — and demonstrate it on Friday to a room that applauds.
Week three
One small change, four days, two things broken that used to work — and nobody who can say what is in there.