Building A DevOps Culture in a Remote World
summary
A cautionary case study: a 30‑day rush to integrate with a new market feature leaves one server running legacy code called Power Peg, a reused feature flag flips inconsistently, and manual deploys across eight machines produce a $460 million loss within 28 minutes. Concrete fixes: delete dead code, create a feature flag per component, run CI/CD pipelines with automated deploys and tests (Azure DevOps cited), centralize clear alerts to avoid 97 unread messages, practice incident response, and put developers on call with open telemetry so people learn from failures.
AI-written summary · about
chapters (8)
- 0:00Intro
- 0:37Emily Freeman
- 2:10Night Capital
- 9:48DevOps
- 12:23Leadership
- 13:13Curiosity
- 14:15Operations
- 15:37Communication
related talks
54mEffective DevOps for Organizations
34mYou only have to change one thing to do the DevOps
17mBeyond DevOps – Holistic transformations in uncertain times
32mTales from the DevOps Transformation Trenches
29mDevOps Anecdotes
30mIf DevOps Is Culture, Why Does Everyone Only Talk About Tools?
01h 02mEffective DevOps for Organizations
26mMission Critical Mindset Building a Culture of Resilience in DevOps Teams