April 29, 2026
New loop, same old argument
Why Software Needs a Third Loop [audio]
Tech says software needs a new step, but commenters say: "uh, we knew this already"
TLDR: The podcast says software teams need a third step after building and releasing: making sure people truly adopt and influence what gets made. Commenters agreed the problem is real, but some mocked it as old common sense being repackaged with a catchy new name.
A podcast chat about why software needs a "third loop" somehow turned into a very familiar internet drama: is this a fresh idea, or just old wisdom with a shiny new label? The hosts argue that putting an app or feature out into the world is only step two — the real missing piece is whether people actually use it, like it, and shape it after it launches. In plain English, they’re saying that releasing something isn’t the same as getting real adoption, and companies need a tighter back-and-forth with users instead of just tossing updates over the wall.
But the comments? Oh, they went straight for the jugular. One reader basically shrugged and said, yes, this is a real problem, because "we hit this at work" too — which gave the whole thing an instantly relatable, office-war-story vibe. Another dropped the spicier take: this all sounds true... but also like something humanity has known since the 20th century. Ouch. That set the mood for the thread: half the crowd nodding along that the problem is real, half rolling their eyes at tech’s endless love affair with renaming common sense.
There’s also a faintly funny meta-joke running through the whole thing: the episode is partly about the power of naming ideas, and the community reaction is basically, "Congrats on inventing a new phrase for listening to your users." That tension — useful framing vs. buzzword theater — is the real show here, and commenters clearly came ready with popcorn.
Key Points
- •The episode explains the reasoning behind the name “Third Loop” and connects it to the hosts’ earlier concept of Progressive Delivery.
- •James Governor says naming is important in technology because it helps unify related practices and make them easier to communicate.
- •The term Progressive Delivery is linked to Microsoft rollout practices described by Sam Guckenheimer, including progressive experimentation on limited cohorts to reduce blast radius.
- •The discussion groups established techniques such as feature flags, dark launches, observability, smoke tests, canarying, and blue-green deployments under a broader delivery model.
- •A central theme is that releasing software is different from achieving actual user adoption, which requires feedback loops and a closer relationship between builders and users.