Ten (Hard-Won) Lessons of the DevOps Transition
summary
Ten concrete lessons on reorganizing teams for end-to-end ownership, replacing gatekeeper approvals with embedded tools, and treating internal platforms like paid vendors. Examples include App Engine’s 3 million apps with 15,000 internal users where charging internal usage forces optimization and produced a 10x reduction in one team’s resource use, and KIXEYE’s split-of-DB responsibilities that drove either a shared persistence service or team-owned DBs. Emphasizes replace approvals with code through libraries, mandatory code review, tests that fail builds, shared on-call rotations, and blameless postmortems.
AI-written summary · about
chapters (15)
- 0:00Intro
- 1:07Reorganize Teams Around Ownership
- 3:53Lose the Ticket Culture
- 5:08Replace Approvals With Code
- 8:09Enforce a Service Mentality
- 9:42Charge for Usage
- 12:26Prioritize Quality
- 16:04Start Investing in Testing
- 17:15Actively Manage
- 18:24Vicious Cycle
- 18:54of Investment
- 19:18Share On-call Duties
- 21:33Make Post-Mortems Truly Blameless
- 24:52Top Five Takeaways
- 25:24What I Could Use Help With
related talks
47mDevOps or DevX – Lessons We Learned Shifting Left the Wrong Way
05mAdventures In Enterprise: Lessons Learned Promoting DevOps In A Legacy Organization
47mOvercoming Obstacles to DevOps
26mLessons Learned from 7 years of Running Developer Platforms
30mAn Evolutionary Approach to DevOps
34mYou only have to change one thing to do the DevOps
29mDevOps Anecdotes
50mDevOps: Top Lessons Learned on Shifting Left For Accessibility and Other Experts