Devops - What does devops culture mean for engineers?
summary
Argues that DevOps is primarily a cultural fix: eliminate the conflict caused when one team must make changes and another must keep systems stable by unify dev and ops into one team that shares responsibility and incentives. Recommends automation (Ansible, Chef, Terraform, CI/CD, containers, orchestration) to reduce toil, institutional learning (books: DevOps Handbook, Phoenix Project, Continuous Delivery, SRE), blameless post-mortems, and practical patterns like central DevOps consultants or rotating guilds; cites LinkedIn pausing development for three months as a real restructure example.
AI-written summary · about
chapters (46)
- 0:00Introduction
- 0:35The way we work
- 0:52Who am I
- 1:06McKinsey
- 1:16Technology
- 2:04Why do I care
- 3:14Problems with DevOps
- 3:37Building things
- 5:10Classical engineering
- 7:16Evolutionary architecture
- 8:28Complex vs complicated
- 11:17Making changes
- 11:39Building faster
- 12:11Higher expectations
- 12:41Making changes quickly
- 13:02Change causes conflict
- 13:33Development team
- 14:08Operations team
- 14:29The biggest cause of instability
- 15:33The secret war
- 16:01Tension against time
- 20:21Traditional organizations
- 21:38DevOps culture
- 21:48The theory behind DevOps
- 23:43Why should we care
- 24:04Conflict
- 24:20Intransigence
- 24:53Its so boring
- 25:17DevOps culture for engineers
- 25:52Learn about devops
- 26:10Recommended books
- 29:45Sharing knowledge
- 30:03Complexity
- 30:36Learning
- 31:13Transformation
- 32:22Institutional learning
- 32:41Fight for it
- 33:38Moving backwards
- 35:04How long can you automate
- 36:26How to build things in devops
- 36:41Elevate the discussion
- 37:30Thank you
- 37:58One question
- 38:38Waterfall and agile
- 38:53The telco example
- 40:45Project teams
