What is DevOps and why should you care?
summary
Argues that DevOps means aligning incentives across dev and ops, not renaming orgs; cites “ten deploys a day” (2009) and Amazon’s >1 deploy/second as outcomes, recommends the Borg paper and Google’s SRE book (readable free) and practices like service level objectives, platforms that embrace continuous partial failure, chaos engineering, and to instrument applications for health metrics. Warns that creating a separate “DevOps” team often builds a second silo, that tools evolve, and that measurable behavior change — not buzzwords — delivers results.
AI-written summary · about
chapters (8)
- 0:00Introduction and welcome
- 1:09What is DevOps?
- 10:52Origins of DevOps
- 18:45Culture and automation
- 25:28Breaking silos
- 31:51Digital transformation reality
- 40:25Transformation challenges
- 42:13Call to action
related talks
41mDevOps for Java Developers (or maybe against them?!)
31mDevOps for Java Developers (Or Maybe Against Them?!)
51mElemental devops
44mDevOps for developers (or maybe against them?!)
54mEffective DevOps for Organizations
38mDevSecOps - what does it mean and where is it taking us?
17mDevOps is not a Factory
20mWhat is DevOps?