Vibe Coding
- 2025
- First edition, 2025
- paperback
- IT Revolution Press
- 9781966280026
AskNex reference artwork. The publisher's cover appears only under an approved rights record.
by Gene Kim & Steve Yegge
An argument that AI assistants change what a software engineer is for, and a set of practices for using them to build production-grade systems rather than demos.
Makes the case for AI-assisted engineering from people who have run large engineering organisations.
AskNex explains and applies the ideas in this book in its own words. Nothing on this page is quoted from the book, and the page does not stand in for it: the argument, the evidence and the voice are the author's, and reading the original remains the deeper path.
The core idea
The scarce skill is no longer typing code but specifying, steering and verifying it. Engineers who delegate well to AI multiply their throughput; the ones who refuse fall behind, and the ones who trust blindly ship debt.
The ideas
2 mental models, in the order they build on each other.
- 01
Chat-oriented programming
Describe the intent, review the result, keep the loop tight. The conversation is the work.
- 02
Context is the product
Output quality tracks the quality of the codebase, constraints and intent you give the model.
What the book argues
AskNex's own paraphrases of the positions this book takes, as they are held in the knowledge graph. Not quotations, and not the whole book.
The scarce engineering skill becomes specifying, steering and verifying; engineers who delegate well multiply their throughput.
Work in a tight loop: describe the intent, review the result, correct, repeat; never accept a change larger than you can read.
Output quality tracks the context you supply: the codebase, the constraints and the intent.
Vibe coding accelerates exploration; production software still needs tests, review and architecture the model cannot own.
AI-assisted software engineering
Specifying, steering and verifying code produced by a model, rather than typing it.
Working with AI
Using a fast, fallible model as a collaborator whose strengths are uneven and must be mapped.
Software quality and review
Correctness, maintainability and safety of software, which a fast first draft does not supply.
Career capital
Rare and valuable skills bought with sustained effort, then spent on autonomy.
Validated learning
Treating a venture as a series of tests rather than a plan to execute.
Where it argues with other sources
Most summaries flatten this. AskNex keeps it, because the disagreement usually decides what applies to you.
Mollick qualified by Kim & Yegge
Expertise is what lets you judge the output; skipping the apprenticeship to rely on the model leaves you unable to evaluate it.
Refusing these tools out of pride or fear now costs more than learning them badly would.
Adopt the tools now, but not in place of the apprenticeship: use them where you can already judge the output, and build the fundamentals unaided where you cannot.
Osmani qualified by Kim & Yegge
The model gets you most of the way quickly; the last stretch of edge cases, integration and correctness is still engineering.
The scarce engineering skill becomes specifying, steering and verifying; engineers who delegate well multiply their throughput.
The leverage is real, and so is the last stretch: delegate the draft, keep the engineering judgement, and budget time for the part the model cannot finish.
What actually matters
- Vibe coding accelerates exploration; production still needs tests, review and architecture the model cannot own.
- The risk of not learning these tools now exceeds the risk of using them.
Where it applies
Practical moves the book supports. Each one is a place to start, not a rule.
- Tighten the loop
Work in small, reviewable increments; never accept a change larger than you can read.
- Feed the context
Write the constraints, conventions and intent down once so every session starts from them.
Questions worth asking
What in my workflow is still typing that should be steering?
Which generated change did I merge without reading?
Problems this book speaks to
Recurring situations where this book is one of the sources AskNex draws on. Each opens a public orientation page.
What are you trying to figure out right now?
AskNex will answer your situation using the ideas in Vibe Coding alongside every other source that applies — including the ones that argue against it.