The DevOps disaster: 15 ways to fail at DevOps
summary
Lists 15 anti-patterns and names concrete failures: conflating continuous delivery with deployment, treating DevOps as a platform team, or as a certification. Describes an implementation using Jenkins, Nexus, Sonar, Puppet on AWS with Amazon Linux, autoscaling and rebuildable production clusters so broken servers are “thrown away.” Insists on measurable CI — every commit triggers a build fixed within ten minutes — and the cultural rule not devops until devs have pagers, plus a year spent fixing culture.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:55DevOps definitions
- 6:21DevOps anti-patterns
- 10:04DevOps roles and access
- 11:32DevOps for enterprises
- 13:18DevOps is not about tech
- 15:28Automation misconceptions
- 16:57DevOps certification myth
- 17:18Automation story
- 20:48DevOps as a culture
- 21:56Agile and DevOps
- 22:18Defining DevOps clearly
- 23:47Management support needed
- 25:18Cultural change takes time
- 26:57Building support
- 28:10Key values of DevOps
- 32:35Q&A
related talks
29m5 ways to screw up your DevOps Transformation
05m5 Pitfalls of Using DevOps to Govern
07mTen Ways to Doom Your DevOps
25mDevOps: Why do we Keep Messing Up?
27mThe curious case of the DevOps engineer and other things ...
39mChallenges Of Devops Adoption
45mDevSecOps Worst Practices
13mTen Ways to Doom Your DevSecOps