Married to DevOps
summary
Argues that DevOps fails when treated as a tools checklist and instead requires culture change, concrete automation and cross‑functional teams. Describes migrations from brittle build scripts to CI systems (including TFS 2005 and Anthill), an early Docker adoption at Accenture, a two‑week CI outage during migration, role‑play that exposes the wall of confusion, and progressive steps: automate pain points, implement CI/CD, make teams responsible for delivery, split services and treat servers as cattle for fast, repeatable deployment.
AI-written summary · about
chapters (12)
- 0:00DevOps journey intro
- 1:23What is DevOps
- 7:29Automation to DevOps culture
- 9:00DevOps culture not tools
- 10:25Wall of confusion demo
- 21:12Defining DevOps today
- 26:59DevOps tools definitions
- 29:51Starting with DevOps
- 33:48DevOps practices evolution
- 36:18DevOps awareness gorilla
- 41:00Pets to cattle in DevOps
- 42:06Selling DevOps to clients
related talks
38mDevOps transformation – the good, the bad and the ugly
27mThe curious case of the DevOps engineer and other things ...
34mDevOps Transformation from the C-Level point of view
32mTales from the DevOps Transformation Trenches
31mCouples Therapy for DevOps and ITIL
53mDevOps and Agility with Visual Studio, Azure and Scrum
15mDevOps - Future of IT
44mContinuous Stupidities - Myths of DevOps