korrents

What Steve Yegge thinks about vibe coding

@steve-yegge · 25 positions · 0 changes of mind

Software engineer of four decades who spent years at Amazon and Google, wrote the Stevey's Blog Rants essays, and co-authored the book Vibe Coding with Gene Kim.

Everything they publish, on ppll ↗

Steve Yegge did not write this page.

We collected these quotes from things they published elsewhere, and every quote links to where it was said. They have no account here and have not endorsed this site. Quotes are word for word; the short line under each one is our own restatement, not their wording. Their own site. Is this you? Claim it or ask us to remove it. Or tell us what is wrong here.

2 dated positions, 2026, in their own words. Our reading of what Steve Yegge has said — not written or endorsed by them.

2 positions so far — this page is not yet offered to search engines.

  1. Our readingA person at maximum vibe-coding speed has about three productive hours a day, and a company that will not let them stop there is going to break.

    Their wordsYou might only get three productive hours out of a person at max vibe coding speed. And yet they're still 100 times as productive as they would have been without AI. So, do you let them work for 3 hours a day? And the answer is yeah, you better.

    ↗From IDEs to AI Agents with Steve Yeggeyoutube.com 16th of 25 in this recording

  3. Our readingA vibe-coded codebase grows heresies: wrong ideas that take root among the agents, keep coming back, and are very hard to weed out.

    Their wordsWhere an idea can take root among the agents that's incorrect. It's It's It's a wrong architecture or or wrong data flow or whatever that's that's causing an impedance mismatch for the rest of your code. And what happens is I call it a heresy because they have the tend They have a tendency to to grow and to come back and they're really hard to weed out, okay?

    ↗From IDEs to AI Agents with Steve Yeggeyoutube.com 20th of 25 in this recording