Elemental devops
summary
Argues DevOps is about five concrete elements — culture, automation, metrics, sharing and continuous improvement — and maps them to practice with examples: Puppet and containers, Google Borg/Mesos, Chaos Monkey, and the SRE playbook. Claims monitoring and service level objectives cut operational hours and cites research that roughly 49% of software cost accrues after launch. Recommends using error budgets, instrumenting app health endpoints, and shifting architecture before automating legacy toil.
AI-written summary · about
chapters (57)
- 0:00Intro
- 2:03Death of Dead Loss
- 8:36The Elements
- 10:48Learning
- 11:36Operations
- 12:25Institutionalized Incentives
- 13:29The secret sauce
- 15:41Oracle 2006
- 17:05Softwares longterm cost
- 17:47What is DevOps
- 19:37Lean
- 20:44Culture Automation
- 21:00Chinese Medicine
- 22:02Lunch or Dinner
- 22:18Western Psychology
- 25:00Alignment Incentives
- 25:26Key Framing
- 26:06Automation
- 27:30Containers
- 28:11The spectrum
- 29:47Who reads the paper
- 31:26Metrics
- 32:09Service Level Objectives
- 35:42Learning Better
- 35:59Different Standards
- 36:43DevOps on your business cards
- 36:53Community of interest
- 37:49Everything is secret
- 39:07Continuous Improvement
- 39:45Pain
- 40:10Five Elements
- 40:22Mixing Elements
- 41:15DevOps Wants
- 41:36Make This Play
- 41:47The Problem
- 42:06The Adoption Curve
- 42:54Tell us what to do
- 43:39You get a choice
- 43:55No one can tell you
- 44:13You have to be willing
- 44:23Fear of following
- 44:55Human blood
- 45:09Damage
- 45:41Five stages
- 46:06Software
- 46:29Services
- 46:45Joy
- 47:00Humans
- 47:19Humans can learn
- 47:35This collected trivia
- 47:49The notion of changing
- 48:02DevOps wont fit your culture
- 48:39Principles are more important than practices
- 49:08Mindset is more important than skillset
- 49:18Best methodology for delivering value
- 49:29Call to action
- 49:51Homework assignment
