Cloud Native Culture
summary
Argues that cloud success fails or succeeds on cultural change not just tech, showing concrete outcomes: companies evolve from “pets” to cattle and adopt CI/CD and SRE, one bank moves to 3,000 releases a month after years of discipline, cautionary incidents include a $100,000 accidental function bill and a 69,000 VM spin‑up, and practices that work are automated pipelines, fitness functions (SLOs like 100ms response or low cyclomatic complexity), consumer‑driven contracts, and “build it, you run it” accountability.
AI-written summary · about
chapters (20)
- 0:00Introduction and background
- 2:05Cloud technology landscape
- 3:09Cultural shift with technology
- 6:00Culture as a barrier to change
- 9:09Organizational inertia
- 11:19Breaking cultural constraints
- 13:05Empowering developers
- 15:12Conway's Law and org structure
- 17:36Legacy systems and heritage
- 21:30Automation and cloud evolution
- 25:23Fear in software development
- 27:50Undifferentiated heavy lifting
- 29:15Speed and disruption in business
- 30:39CI and continuous delivery
- 34:16Site reliability engineering
- 37:46Balancing speed and safety
- 40:13Developer autonomy and accountability
- 43:03Evolutionary architectures
- 47:39Change management and empathy
- 51:32Technical debt and failure modes
related talks
42mCloud Native Applications
44mNine Ways To Fail at Cloud Native
43mSoftware Eats Culture For Breakfast
30mHow to beat an existential crisis by becoming Cloud Native.
34mCloud Native: The Cattle, the Pets, and the Germs
11mOpening Words
30mCloud & DevOPS culture
37mCloud Native Technology and Cultural Context: Maximizing Business Value Across...