Pick a Lane: The fallacy of generalists-only in DevOps
summary
Argument: a “generalists-only” DevOps model fails because one-liners from Stack Overflow and duct-tape fixes create recurring outages, lost velocity and hidden tech debt. Concrete pain points include Docker/containers (even docker-in-docker traps), a library with a memory leak, an exploitable CVE, and a rising champagne factor when expert knowledge leaves. The alternative is teams of specialists who negotiate tradeoffs, document decisions, and rebuild trust so onboarding speeds up and outages drop.
AI-written summary · about
chapters (11)
- 0:00Intro
- 1:44How did we get here?
- 3:42Duct-tape solutions
- 5:12Failures
- 5:51Time
- 7:41There is no I in team.
- 9:37Champagne factor
- 11:01People-shaped people
- 13:16Communication
- 15:07Empathy
- 17:06Trust
related talks
27mThe curious case of the DevOps engineer and other things ...
11mDevOps Pitfalls, Beyond The Technology
44mContinuous Stupidities - Myths of DevOps
34mThe Return of the Dull Stack Engineer
48mNew barriers for DevOps adoption
47mDevOps is for Product Engineers, too.
05m5 Pitfalls of Using DevOps to Govern
30mAdopting DevOps? You are aiming at the wrong target!