The DevOps Revolution: We Haven't Always Known Everything
summary
Proof shows over-specialized tooling and jargon block talent: about 90,000 new grads a year face documentation that assumes deep context, job ads demand impossible experience, and onboarding is inconsistent. A demo cuts car firmware updates from hours to about 45 minutes (or seconds for app patches), proving rapid capability gains if teams teach. Concrete fixes are mentoring, hiring seniors who mentor juniors, and shipping a useful quick start with a practical example instead of terse, expert-only docs.
AI-written summary · about
chapters (24)
- 0:00Intro
- 0:50Meet Kat Cosgrove
- 2:34Embedded Linux
- 4:52DevOps
- 5:20Tools Cultural Shift
- 7:18Its Not Just DevOps
- 7:46The Problem of Expertise
- 10:29The Problem Scale
- 12:48Gatekeeping
- 13:58Intentional Gatekeeping
- 15:40Fencing
- 18:31Goats
- 18:50Overwatch
- 21:47Esports
- 23:30Technical Documentation
- 25:26Easy
- 27:21Mentors
- 29:31Seniors
- 30:17Junior Engineers
- 30:47Job Postings
- 35:06The Cultural Problem
- 36:55Why DevOps Exists
- 37:55Questions for You
- 39:15Question for the Stream
related talks
34mDevOps - The Next Generation
20mJourney Of Devops Teams in a Corporate Environment
37mDevOps for Java Developers (Or Maybe Against Them?!)
25mDeveloper Experience is central to DevOps success
05mDevOps over time
20mDevOps so easy, anyone can do it
22mOperationalizing DevOps Teaching
25mDevOps Handbook Experiments in Accelerating Delivery