Vibe Coding's head chef ages better than its tools
Kim and Yegge's Vibe Coding ages fastest in its tooling chapters, but the head chef is the part worth keeping: you can't blame the sous chef for what leaves the kitchen.
Imagine you’re the head chef in a busy professional kitchen. You have a brigade of sous chefs working for you, and they’re faster than any human cook. A customer sends back a plate of overdone fish. That plate is your plate. You can’t blame the sous chef for what comes out of the kitchen.
This is the central image of Gene Kim and Steve Yegge’s Vibe Coding. It’s an idea that’s really stuck with me.
In this kitchen, you’re doing a lot less personal chopping. Instead, you’re running the line: managing multiple cooks at once, tasting every plate before it goes out, making sure they all meet the same standard so the dishes work together. Kim and Yegge describe this as the work that used to fall to a team lead, but now rests on one person and a few agents. (Mike Hadlow points out it works best if you know how a real brigade is organized.) The difference from a real kitchen is that these cooks never clock out and never stop asking for the next ticket. So it’s your attention that runs out first.
This is already how I work. In Running an agent fleet like a small team, I described how I give each agent a role and run every change through a review gate before landing it. The agents propose, I decide.. that’s the head chef’s job at small scale. Everything that comes out of my kitchen is still mine, and I talked about ownership in Who owns the code Beyond Vibe Coding held up against 2026.
The tooling for agents changes with every model release, but directing cooks and tasting plates doesn’t. If the part of a vibe coding book that sticks around is how you manage a kitchen, was it a management book all along?