Steve Yegge

speaker

592 appearances 1 recordings 1 series first heard Dec 2025 last heard 26 Dec

Steve Yegge’s voice in public audio — every appearance, attributed to the second.

Trend

recordings per month · last 12 months

Recordings per month over the last 12 months — 1 in all, peaking in Dec 2025 with 1.

Appearances

newest first · ▶ plays the moment

Latent Space: The AI Engineer Podcast · Steve Yegge's Vibe Coding Manifesto: Why Claude Code Isn't It & What Comes After the IDE · 26 Dec 2025 podcast

Last year we were trying to get people to write with chat, right?

And we were like we're telling and they were like, no.

completions and we're like oh god no but it can generate the code and you just gotta paste it in and you just gotta do all this stuff and they were like that sounds kind of hard and we're like but it's faster and they they wouldn't do it and then nine months later it finally percolated in and now they're all like I like cursor and it's like that's so last year dude right like wake up and yet they haven't adopted it and so you have to at this point look at it and say why haven't they adopted it?

Let's go look at the reasons and the answer is it

It's too hard.

You have to be able to read.

Man, most engineers honestly, like to them, five paragraphs is an essay.

Okay.

And with cloud code, you've got to read waterfalls of not just information but also code and diffs, right?

Because if you're gonna put your IDE away, you actually do have to look at the diffs.

Now, I'm gonna tell you that once you get some expertise at this, you can actually tell from the shape of the diffs and the color of the diffs and the

length of the diffs, the vibe.

You can tell whether it needs a code review, whether they're doing the wrong thing, whether they seem to be writing suspiciously too much code for this problem.

Right?

The diffs alone, just the shape of the diffs can tell you a lot about what's going on without actually reading the code.

But you should pay attention to them.

Otherwise you'll have problems that will only crop up later, right?

But yeah, I mean like uh uh uh put the IDE away.

Uh okay, clog code and then get clogged code out and try to start using it, all right?

Showing 201–220 of 592 · page 11 of 30