"Doing Devops" as a politically powerless developer
summary
Argues that developers can start DevOps without executive buy‑in by shipping concrete changes: write tests and use feature flags, automate a local pipeline with tools like Octopus Deploy or TeamCity and Azure, and prefer trunk‑based development to avoid long merges. Cites DORA data from 27,000 organizations (high performers deploy in minutes/hours, low performers every 3–6 months, high performers spend ~44% more time on new work) and examples like Git VFS for a 270 GB Windows repo to cut clone times; measure cycle time and show Gartner/DORA numbers to management.
AI-written summary · about
chapters (28)
- 0:00Intro
- 0:20Damian Brady
- 3:00The problem with DevOps
- 4:56What is DevOps
- 6:54Technical stuff
- 14:11Feature flags
- 17:13Excuses
- 19:42Its too hard
- 21:19Continuous isolation
- 23:33Automation
- 25:57Pipeline
- 28:05Power Loom
- 29:43Treating software as a product
- 31:35Changes to process
- 33:35Management buying
- 35:31Analysis
- 37:09Measure
- 40:45Dont ask permission
- 42:22Business is the bottleneck
- 43:47SCADA
- 44:37Gartner
- 45:20Puppet
- 46:33DevOps Report
- 48:23Working with Manager
- 49:43Not everything is going to be rosy
- 50:04Change failure rates
- 51:34The good news
- 54:21Questions
related talks
41mDevOps for Java Developers (or maybe against them?!)
54mEffective DevOps for Organizations
46mDevOps for Java Developers (or maybe against them?!)
01h 02mWe have DevOps. No one was fired. But what to do?!
51mSelling DevOps
34mYou only have to change one thing to do the DevOps
55mDevOps isn't just about developing
44mDevOps for developers (or maybe against them?!)