5 Pitfalls of Using DevOps to Govern
summary
Covers five concrete failure modes: overprescribed architecture templates that reject apps using different compute or databases, abstraction wrappers around CI/CD that hide logs and prevent troubleshooting, a pipeline full of scans that turns builds into compliance chores and blocks releases, duplicated controls from indiscriminate shifting left that blocks builds, and choosing security as the primary customer at the expense of developer productivity; recommends self‑service tooling and deliberate placement of checks to keep both security and delivery fast.
AI-written summary · about
related talks
29m5 ways to screw up your DevOps Transformation
07mTen Ways to Doom Your DevOps
13mTen Ways to Doom Your DevSecOps
33mThe DevOps disaster: 15 ways to fail at DevOps
45mDevSecOps Worst Practices
11mDevOps Pitfalls, Beyond The Technology
25mDevOps: Why do we Keep Messing Up?
29mDevSecOps: Five Common Mistakes