SS Stephan Schmidt On Arrested DevOps

“Bottleneck 1.0 has been for the last 20 years kind of engineering. Everyone who wanted something on the website or something programmed needed to get into some kind of backlog, and then waited, and then sometimes heard that can't be done. … But now that everyone wants to deploy to production, it needs to be reviewed and you get into a review queue. Obviously, the person can build it on their own until they like it, but then they still need to wait. That's what I call bottleneck 2.0.”

Arrested DevOps · Software Engineering & Infra · November 2026

“Bottleneck 1.0 has been for the last 20 years kind of engineering. Everyone who wanted something on the website or something programmed needed to get into some kind of backlog, and then waited, and then sometimes heard that can't be done. … But now that everyone wants to deploy to production, it needs to be reviewed and you get into a review queue. Obviously, the person can build it on their own until they like it, but then they still need to wait. That's what I call bottleneck 2.0.” — Stephan Schmidt, Arrested DevOps

Context

Matt asked Stephan to explain the term "bottleneck 2.0" he had used before the show. Stephan defines it against the old engineering backlog.

Transcript

Arrested DevOps Around 05:19 into the episode
Tanya Higgins

…generator in there, email signature generator in there. It's just totally grown and adoption has been great. Now there's clawed skills for it. So just really the sky's the limit. And it's made my life so much easier as a designer on a very small team to not be asked for assets every single day.

Matt Stratton

…when we were talking before the show about this idea of you call it bottleneck 2.0. So can you tell us a little bit about that? And then how does this, you know, we just talked about the dream, you know, hey, designer, push the thing. So let's talk about the challenges and what this brings in.

Stephan Schmidt

I think that the term neural factor bottleneck 2.0 refers to bottleneck 1.0, which is for the last 20 years has been kind of engineering. Everyone who wanted to get something in the internet or something programmed or on the website usually needed to get, at least since agile, needed to get into some kind of backlog and then waited for some time and then sometimes heard that can't be done. And that kind of is though with AI, because everything is faster. But now that everyone wants to deploy to production, it's now like, okay, before we can put that into production, it needs to be reviewed and you get into a review queue. And to some, so there are a lot of benefits. Obviously, the person can build it on their own until they like it, but then they still need to wait. And that's kind of what I call bottleneck 2.0.

Matt Stratton

So when we think about non-engineers, and I'm just, again, to be very clear for everybody listening, there is no shade in that term. I'm just sort of saying people who do not, you know, have a software engineering background when it comes to that. So non-engineers shipping with AI. So like you…

Stephan Schmidt

I start with the sideways. One more fun part. Yeah. Depends on whether you're responsible for it or not, for the sideways. But I think the sideways thing shows up mostly in shadow apps and maintaining security. So everyone deploys somewhere. They can't deploy to the production system of the…

Matt Stratton

Right, exactly. And it's so much easier. And even it's like you said, I kind of love where you're saying it's bottleneck 2.0. Like these are not new problems. They're just happening at a greater scale because in the early era of cloud, we had the exact same shadow IT problem, which was the, oh…

Speaker names come from our own diarization. The position is estimated from where the line sits in the episode.

More from Arrested DevOps