SS

Stephan Schmidt

Things Stephan Says on Podcasts

Where to Find Them

Stephan Schmidt has been a guest on Tech Lead Journal (2 times) and Arrested DevOps .

Recently: “Marketing Ships to Production with Stephan Schmidt and Tanya Higgins” on Arrested DevOps (November 2026); “CTO Coach: Why Tech Companies are Really Laying Off Developers (It’s Not Just AI)” on Tech Lead Journal (January 2026); “#186 - The Amazing CTO's Missing Manual: Guide to Managing Tech Teams - Stephan Schmidt” on Tech Lead Journal (August 2024).

What They Said

“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

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

Arrested DevOps · 2026-11-18 Permalink → Listen →
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.
“Because there is some kind of bottleneck, the AI always helps you. It says, oh, you can't deploy to the company site? Well, we can deploy it to Vercel or we can deploy it anywhere. … I've seen CEOs who deploy to Vercel, who deploy wherever they like. And no one knows what's running where.” — Stephan Schmidt, Arrested DevOps

Matt asked where non-engineers shipping with AI works and where it goes sideways. Stephan says the sideways case is shadow apps: when the official path to production is blocked, the AI agent suggests another host.

Arrested DevOps · 2026-11-18 Permalink → Listen →
Arrested DevOps Around 06:50 into the episode
Stephan Schmidt

…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

…the same thing. It still needs to be reviewed. You're like, wait a minute, I coded this awesome thing. And what do you mean? Now it's not sitting here. So like this idea of these folks doing this, where does that, where does it work effectively? And how does it go sideways maybe when it doesn't?

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 company. They deploy to Versal. They deploy to whatever the AI thinks is a good idea to deploy to. I think that is where it goes sideways, where people, because there is some kind of bottleneck, it just, the AI always helps you. It says, oh, you can't deploy through the company side. Well, we can deploy it to Versal or we can deploy it anywhere. So that's, I think, is where it goes sideways, where the bottleneck basically pushes everyone to deploy just somewhere else. And I've seen CEOs who deploy to Versailles, to CEOs who deploy wherever they like. So that's where I think where a lot of things happens where and no one knows what's running where.

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…

Tanya Higgins

Yeah. I think a lot of it I had to, it was an adjustment for me to get comfortable with being uncomfortable because I'm not going to understand absolutely everything that's happening. Like I don't have a background in code. I'm still spending, I'd say some days I'm fully in terminal in Ghosty doing…

Matt Stratton

I think that there's a responsibility on engineering or sysadmin, whoever, the people who care about, you can't just say do it the right way. You have to enable for that. And so often, and this is, I mean, recording episodes of this show, I continually keep going back to this same old well of like…

Speaker names come from our own diarization. The position is estimated from where the line sits in the episode.
“The company already solved this with your phone. You run apps from people you don't know, and they are next to your banking data, and no one is worried. So why are you allowing people to run stuff on your phone, but not let people run stuff on your production system?” — Stephan Schmidt, Arrested DevOps

Host Matt Stratton had asked how engineering and security can enable non-engineers (marketing, product, CEOs) to ship software with AI without losing control of production. Stephan offers the phone's app-permission model as a mental model he uses with clients.

Arrested DevOps · 2026-11-18 Permalink → Listen →
Arrested DevOps Around 11:24 into the episode
Tanya Higgins

…even if I forget it, everything is okay. So there's always just like a back door of everything going to be okay, because that's already been thought through. Like all the worst case scenarios have been thought through. So this thing is really bulletproof with me being able to push and do things.

Matt Stratton

…And we in engineering have not really thought about like how you market that and share that and communicate that outside of your department. So what are the ways to solve for that? Or what have you kind of seen about doing that? Because I imagine that's a key part of unblocking that bottleneck.

Stephan Schmidt

Yeah. One thing, one mental model that helped me a lot and helps clients a lot in discussing this is basically we already, the company already solved this with your phone. So you on your phone, you run apps from people you don't know and they are next to your banking data and no one is worried. So why are you allowing people to run stuff on your phone, but not let people run stuff on your production system? And if you look into this, there are some attributes to the phone that can. Carry over to normal development, which is, for example, app permission. If you usually, if someone writes some code, it can do everything. It can delete the orders, it can delete customers, it can read all the customers, it can do everything. If you model it with permissions, then Tanya could write something and it could be deployed, but her app or her module or her package does not have the rights to read all the customers. And then there's no need to review the code if it does this. You just need to review the permissions. You're just like the phone pops up. Can I read…

Matt Stratton

Yeah, I think it keeps going back to that these are solved problems, but the scope of where they have to be extended to, you know, because we think about things like safety two. And the idea is if we look at a blameless and a safety two concept is when something bad happens, it's not what did Tanya…

Tanya Higgins

That was like four questions all in one. Yes, it was. Okay. We're going to start with question one, which is, let's go back actually. Can you repeat to me, Matt? Yeah, the first one was too many. What are

Matt Stratton

some things you understand more now about engineering and building systems and stuff that just you didn't sit down and read a book, you know? No, I didn't

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

Collections They Appear In