The curious case of the DevOps engineer and other things ...
summary
Argues that the DevOps engineer myth is real: job adverts expect impossible full‑stack mastery, so hiring fails. Shows tooling fixation — Jenkins pipelines and CI/CD toolchains get bought but culture and measurement lag, so most organizations see low success in promised speed and quality. Gives concrete failure modes: broken test pipelines, chaotic incident calls, postponed security until CVEs, and repeats the Kubernetes mistake — Cloud native ≠ Kubernetes — advises baby steps and measurable foundations.
AI-written summary · about
chapters (15)
- 0:00Introduction and background
- 3:16DevOps as culture vs tools
- 5:07Myth of the DevOps engineer role
- 7:37Separate DevOps teams and overhead
- 9:03Tooling obsession over process
- 12:15Flaws in DevOps training and roadmaps
- 13:59Silos and crisis mismanagement
- 16:50Haste and broken pipelines
- 17:55Baby steps over big bangs
- 18:39Security as an afterthought
- 20:03Cloud native repeating mistakes
- 21:48First principles and foundations
- 23:13Measured transformation over sprints
- 25:00Cultural shift beyond tools
- 26:03Q&A and closing remarks
related talks
48mNew barriers for DevOps adoption
17mDevOps Leadership in practice. True stories
25mDevOps: Why do we Keep Messing Up?
24m7 DevOps Myths
11mon unrealistic expectations in DevOps
29m5 ways to screw up your DevOps Transformation
44mContinuous Stupidities - Myths of DevOps
44mDevOps for developers (or maybe against them?!)