How DevOps is evolving practice
summary
DevOps starts as tearing down the ticketing “wall of confusion” and now shifts from speeding deployments to resolving architecture, product and security bottlenecks; organizations with CI/CD pipelines find the next constraints are monolith decomposition, observability and governance. Concrete practices to adopt: use SLOs and error budgets, treat architecture as a product, and apply observability and DevSecOps. Key skills are cognitive estrangement, noticing/framing, and metacognition. Warning: practices usually spawn tooling, not the other way around—don’t just lift-and-shift containers, Kubernetes or cloud into old processes.
AI-written summary · about
chapters (8)
- 0:00Introduction and background
- 2:27Origins of DevOps and the wall of confusion
- 7:04DevOps as mutual skill improvement
- 11:38Shifting bottlenecks in DevOps adoption
- 15:49Expanding DevOps conversations
- 24:09Core skills for DevOps practice
- 31:17Technology adoption pitfalls
- 35:31DevOps as a way of thinking
related talks
24mHow DevOps changed the way we operate software
39mWhat is next for DevOps?
16mDevOps - Philosophy vs Practice
28mDevOPs Lessons for Frontend Developers
19m10 years of DevOps - Where Are We Today?
30mIf DevOps Is Culture, Why Does Everyone Only Talk About Tools?
34mYou only have to change one thing to do the DevOps
40mHow did our DevOps team become another silo?