Funny Stories and Anti-Patterns from the DevOps Landscape
summary
This talk examines concrete DevOps anti‑patterns and real postmortems, arguing that creating a separate DevOps department or hiring a single “DevOps” person often fails to fix culture. It gives anecdotes where Docker and containers hide failures, and where automation (Terraform, Ansible, Jenkins, Kubernetes) and roles (SRE) either improve operations or cause rot, explaining what was built, why deployments and incident workflows broke, and when fixes succeeded.
AI-written summary · about
chapters (11)
- 0:00Talk overview
- 3:53What DevOps really is
- 7:46DevOps department story
- 14:49Magic DevOps story
- 21:05Renaming roles story
- 26:03Role separation
- 31:40Tools misconceptions
- 36:11Incident management
- 42:28Magic developers story
- 46:01DevOps diversity
- 49:31Recommendations
related talks
17mDevOps Leadership in practice. True stories
33mThe DevOps disaster: 15 ways to fail at DevOps
27mThe curious case of the DevOps engineer and other things ...
32mTales from the DevOps Transformation Trenches
40mDistilled Abnormal DevOps Iterations
45mMarried to DevOps
55mPatterns & Anti Patterns for Scaling & Enabling DevOps Adoption
29m5 ways to screw up your DevOps Transformation
