Vibe Coding: Building Production-Grade Software With GenAI, Chat, Agents, and Beyond

Book Review: 4/5 Impact On Me (Gene Kim, Steve Yegge)

Read more about the book here.

This book had a 4 out of 5 impact on me. The title felt clickbait, but the content delivered real substance. The author is well-known as the author of The Phoenix Project and The Unicorn Project, so I was eager to read it. I picked it up while I was vibe coding day and night and building AI systems at work. Much of the content was not new to me, but it reinforced AI context engineering beliefs I was already forming and priorities I was setting for my product team.

The author says coding is fun now. You worry less about the pain and get to focus on the enjoyable parts. AI handles the complicated or tedious tasks and can refactor code for you. You stay in charge of direction, product features, and benefits. I found this true, and loved the author's description and examples. That added weight to how I see knowledge work going: you have less excuse to avoid doing something or to not know something. At home we have largely stopped leaving it at "I don't know"; we add "but I can look it up with AI." The authors talk about this kind of shift too. With vibe coding, whether you have a process automation, a web app, or a new concept in mind, AI can help you get there.

The authors' claim that programming and building products are undergoing a structural change, and that this is not a fad. This resonated with me. They mention you can be faster, more ambitious, more autonomous, and have fun by using AI in your work, and I am experiencing that. The concerns they raise about vibe coding going rogue made sense, but most of that was not new to me. They also describe using a vibe-coding approach for knowledge work (documentation, analysis, research), not only coding, which aligned with how I use AI. A tech blogger coined "vibe engineering" as a more thought-through version of "Vibe coding" -  that idea appealed to me. Authors also say if you vibe code with blinders on and do not read what is happening or think things through, you still will not get a good product. You cannot fall asleep at the wheel. You also start thinking in terms of conversations as your units instead of code, functions, or files.