Cloud Native Culture
summary
Argues that culture, not just tools, determines cloud success, citing the Bezos mandate (everything exposed as APIs with firing as incentive), real cost shocks (a forgotten function racks up ~$100k), and a case of thousands of releases a month at a bank. Recommends concrete moves: adopt CI/CD pipelines, treat servers as cattle with containers and managed cloud services (Heroku/AWS/App Engine/Cloud Foundry), create paved roads and SRE practices, and enforce build it, you own it accountability — yields a reported 60% cost drop when unused resources are removed.
AI-written summary · about
chapters (16)
- 0:00Introduction and speaker background
- 2:19Why culture matters in cloud adoption
- 8:56Microsoft’s culture transformation example
- 12:04Changing culture through persistence
- 15:14Conway’s law and team structure
- 17:39Technology change vs culture change
- 20:45Cloud native practices and automation
- 25:57From pets to cattle in infrastructure
- 31:11Speed and responsiveness in modern tech
- 32:35CI/CD pipelines and small batches
- 37:49Automation and SRE fundamentals
- 42:49Managing technical sprawl
- 47:21Developer accountability and ownership
- 48:28Post-mortem culture and learning from failures
- 52:19Empathy in driving organizational change
- 56:52Patience and progress over perfection
related talks
42mCloud Native Applications
11mOpening Words
44mNine Ways To Fail at Cloud Native
31mCloud native: the cattle the pets and the germs
06mAccelerate Application Delivery with a Cloud-Native Mindset
33mWhat the Cloud?
05mCloud native or cloud agnostic? The questions you need to ask
34mCloud Native: The Cattle, the Pets, and the Germs