Heavybit podcast episode unpacking the “Third Loop” concept: breaking the wall between software makers and software users, extending DevOps beyond Dev+Ops.
Key Takeaways
Progressive Delivery packages canary releases, feature flags, dark launches, and observability into a named concept; the name came from Microsoft Azure DevOps progressive experimentation work by Sam Guckenheimer.
DevOps broke the Dev/Ops wall; the Third Loop argues there is a second wall between builders and users that observability and progressive rollout close.
“Never Finished” was a rejected podcast title capturing the same idea: web-delivered software has no true release point and is always being tweaked.
The urgency for the Third Loop increased because software is now embedded in cars, tractors, and household devices, meaning non-technical users cannot opt out of updates.
Naming things gives teams shared vocabulary: without a name like Progressive Delivery, explaining the concept required an hour-long conversation every time.
