Vibe Coding
Where Yegge's essays argue that the way we write software is changing, this book is the how-to. It's a collaboration with Gene Kim — the person who spent a decade codifying how good engineering orgs actually work — aimed at teams that want the productivity of agents without surrendering their judgment.
What it is
A full-length book, published by IT Revolution on October 21, 2025 (ISBN 9781966280026), titled Vibe Coding: Building Production-Grade Software With GenAI, Chat, Agents, and Beyond. The authors are Gene Kim and Steve Yegge; the foreword is by Dario Amodei, CEO and cofounder of Anthropic. (Some retailer listings credit Amodei as a third contributor — that's the foreword.) It won a 2026 Axiom Book Awards Gold Medal.
The pairing is the point. Yegge brings the frontier-practitioner voice from Google, Amazon, and Sourcegraph; Kim brings the organizational lens from two decades of DevOps writing. The publisher's own framing leans hard into the shift:
"Science fiction is now reality. Programmers no longer need to toil over code and syntax. They can now describe what they want and watch it materialize instantly."— Vibe Coding, publisher description (IT Revolution)
The thesis
Building real software with agents is a discipline, not a vibe. The provocative name is deliberately at odds with the subtitle — "production-grade" is the whole argument. The claim is that when intent and flow matter more than syntax, a developer can operate at a different altitude: describing outcomes and supervising an agent that fills in the implementation. Done well, that's not reckless; it's a new craft with its own practices.
The authors organize the upside as five dimensions of value, given a memorable acronym:
"vibe coding creates value across five dimensions, which we've named FAAFO—fast, ambitious, autonomous, fun, and optionality."— The Value of Vibe Coding (or, the Good FAAFO), book excerpt (IT Revolution)
The framework / what it teaches
The book runs in four parts: the case for vibe coding; the theory and practice (using a chef / sous-chef metaphor and the problem of "context saturation"); the tools and agents, and how the classic code–compile–run–test–debug loop transforms into a conversation with the model; and finally the organizational culture shifts needed to get the most from it. Two working models carry the practical weight:
- FAAFO — the value scorecard. Fast (hours instead of days), Ambitious (not-worth-it tasks become quick wins), Autonomous (fewer handoffs and coordination costs), Fun (building instead of wrestling syntax), and Optionality (explore approaches in parallel; one-way doors become reversible).
- The three developer loops + Prevent–Detect–Correct — the control scorecard. Across the loops the book teaches task decomposition, strategic checkpointing, and rigorous verification so you catch the failure modes agents actually produce: silently deleted or hacked tests, 3,000-line monolithic functions, a near-accidental branch deletion.
The recurring instruction is supervisory judgment — knowing when the agent is confidently wrong and pulling it back:
"vibe coders must learn to notice when AI is heading confidently down a wrong path and decide when to redirect or abandon unproductive approaches."— The Value of Vibe Coding (or, the Good FAAFO), book excerpt (IT Revolution)
Where it sits in Yegge's arc
This is the book-length version of the AI-era essays. The Medium pieces — The Flat Curve Society and its siblings — are the provocations: the way we build software is being rebuilt, and you'd better become AI-literate. Vibe Coding is where those arguments get a method. It answers the question the essays leave open — fine, so how do I actually ship with this? — by pairing Yegge's frontier voice with Gene Kim's organizational rigor and turning "trust the vibes" into a set of checkable practices.