Coding Stopped Being the Bottleneck. So What Replaced It?

Welcome to TechPod Talks.

I'm Stephen Koza, CEO at EverOps.

This is the show for engineers and technical leaders in the trenches, the people building platforms, running cloud, scaling infrastructure, and figuring out what's next.

Every episode, I sit down with somebody who's actually doing the work to get the real story.

No theory, no fluff, just what's working right now.

Let's get into it.

Every engineering team in the world just got the ability to write 10 or even 100 times more code, but almost none of them are shipping 10 times the value.

Why? Well, coding's not the bottleneck.

It's everything else.

The reviews, the testing, the rework, the waiting.

Now that AI has flooded the system with more code than people can possibly review, you got a fork in the road.

Either you figure out how to remove humans from the loop or watch somebody else do it first.

I'll

tell you, like, any engineer that's experienced will say, like, more code's not better.

It gives me, like, no hope to say we're going to generate a ton of code.

I would actually feel a lot better to say, like, we've actually found a way to generate less code and have a less surface area for attacks.

So that was me in April, episode two, and that's Meyer Wasserman a few episodes later telling me I got it wrong.

I'm Stephen Koza.

I run a cloud and AI services firm called EverOps, and this is TechPod Talks.

We're 10 episodes in, 10 people who actually run engineering orgs.

I asked them all basically the same question.

If writing code stopped being the hard part, what about now? And I thought I would get more agreement than I got.

Google's DORA team asked 5,000 engineers that same thing.

And same split.

AI has pushed up throughput, but stability has gone down.

And at the same time, things are faster, shakier, and nobody's solved for that yet.

So what you're about to hear doesn't quite line up.

A couple of these guys flat out contradicted each other.

But the part they do agree on is the part I didn't see coming.

Let's get into it.