pull down to refresh

DevOps guru and ex-Googler say vibes beat reading diffs but there are risks
"Accept All. Always. Don't read the diffs anymore."
This is OpenAI co-founder Andrej Karpathy's vision of "vibe coding" as he described on X in February – a new approach where developers surrender control to AI agents and simply trust the vibes.
Karpathy did not advocate vibe coding for production, describing it as "not too bad for throwaway weekend projects."
Now Gene Kim and Steve Yegge have written the book on it, and they want to persuade coders this isn't madness, but the future of software development.
Kim is a researcher into high-performing technology organizations, well-known for his books on DevOps, and Yegge is a software engineer and blogger, formerly at Amazon and Google, and these days working on AI coding tools at Sourcegraph.
The authors state in the preface that "vibe coding seems to be reinventing the foundations of how we build software." They have set out to convince skeptics by describing their own learning journey, targeting the book at "any developer who is building things" as well as product owners and infrastructure engineers.
Do the authors even put into practice what they preach? If they had a mission critical project would they vibe code it? Do they have vibe coded projects in production that people are using satisfactorily?
reply
I think they know the limitations pretty well, since they're the experts, and you can kinda tell that from the review. Maybe they don’t wanna go too deep into the problems with vibe coding because they’re trying to sell their stuff, and if they say it’s rotten, no one’s gonna buy it.
reply