The End of the Beginning
summary
Argues that DevOps is proven by specifics: Cloud Foundry and Puppet work reduce human-hours growth versus old ops, Google’s SRE practices codify embracing risk, service level objectives, eliminating toil, and real examples show behavior must change to count. Uses evolution and scale analogies — punctuated equilibrium, square–cube limits (an ant cannot scale to elephant size), a cited 5,000× lift fact — to explain why processes and orgs that work at one scale fail at another.
AI-written summary · about
chapters (43)
- 0:00Intro
- 1:00Andrew Clay Shafer
- 1:57The most important slide
- 2:09Werewolf guy
- 2:27Engage
- 2:45Great Talks
- 3:00Nash Equilibrium
- 3:59The Mountains
- 4:15Where are we
- 6:23Not everyone wants DevOps
- 6:52There is better things happening
- 7:23DevOps is a word
- 10:01Softwares eating the world
- 10:25Optimizing human performance
- 11:14Bash
- 11:33Everyone wants DevOps
- 12:00Missing context
- 12:54Evolution
- 14:27Game Theory
- 15:32Cell Structure
- 16:38Organ Systems
- 17:21Systems of Systems
- 18:23Ants
- 19:37Elephants
- 19:58Time eating
- 20:08Elephant sized ants
- 22:13Nodes
- 22:54buzzwords
- 23:10single dominant emergent paradigm
- 23:35continues continually
- 24:02Reliability Engineering Book
- 24:41Homework
- 25:08Google
- 25:44Patterns of success
- 26:12Happy DevOps
- 26:26Culture vs Automation
- 27:08Understanding DevOps
- 27:33Organizational Learning Dynamic Process
- 28:33Flying by the Seat of Our Pants
- 30:24The End of DevOps
- 31:15Conclusion
- 31:41Darwin Quote
- 32:09End of the Beginning
related talks
51mElemental devops
48mUse DevOps to identify, embrace, and drive exponential Change
30mSurviving DevOps
22mThe Journey to DevOps: What I Learned
44mDevOps for developers (or maybe against them?!)
45mWhat is DevOps and why should you care?
30mAn Evolutionary Approach to DevOps
33mWhat Got Us Here Won’t Get Us There: A Story of Transformations