Looking Back At 13 Years Of DevOps
summary
Starts from a 2009 meetup of 60–70 people in Ghent and traces 13 years of repeating patterns: golden images and manual changes cause config drift, teams reintroduce manual edits, and long-running branches and UI provisioning break reproducibility. Recommends three concrete tool classes—Terraform, Puppet, Ansible—for provisioning, desired state and orchestration, urges idempotency, a single source of truth, environment-isolated stacks, CI for infra code, and fewer bespoke scripts; claims DevOps’ original values are diluted and recovering them requires swapping specific anti-patterns for these practices.
AI-written summary · about
chapters (16)
- 0:00Introduction to DevOps journey
- 1:03Early DevOps conference origins
- 2:29From manual servers to automation
- 4:15Evolution of infrastructure as code
- 7:25Solving configuration drift with IaC
- 10:18Three types of infrastructure tools
- 12:22Why implement infrastructure as code
- 13:45Common automation anti-patterns
- 17:57Dangers of non-idempotent tools
- 21:05Stacks and environment isolation
- 23:55Testing and CI/CD in IaC
- 25:42Git repository pitfalls
- 27:05Leveraging open source tools
- 28:30Why long-running branches fail
- 29:57DSL vs full language trade-offs
- 31:01Key lessons and next steps
related talks
56m14 years of #devops, but what did we really learn
27m10 years of #devops, but what did we really learn?
48mOver a decade of #devops, what have we learned
44mDevops - Almost 10 Years - What A Strange Long Trip It's Been (Keynote)
49mDevOps Ten Years After: Review of a Failure with John Allspaw and Paul Hammond
19m10 years of DevOps - Where Are We Today?
26mThe Timeless way of DevOps
49mTen Years of the DevOps Movement - A Retrospective and Outlook