The Return of the Dull Stack Engineer
summary
Argues for a return to the Dull Stack Engineer who knows what’s running on his platform and prioritises operability over chasing new shiny tools. Shows how widespread Docker Kubernetes Puppet Chef Vagrant OpenStack and Vault adoption often happens without production experience leads to pager nights and fragile platforms. Documents failures: pilots that work on laptops but not at scale, divorced DevOps teams, and two-speed orgs. Proposes rebuilding resilience through collaboration, runbooks, monitoring and conservative tooling choices.
AI-written summary · about
chapters (12)
- 0:00Start
- 2:3910 days into operations
- 3:04Topic Evolution: Culture
- 4:14Topic Evolution: Automation
- 5:41Topic Evolution: Monitoring
- 8:19Why adopt shiny new stuff?
- 14:57Improve your sleep
- 16:29Puppet Adoption
- 18:28Workload is inverted
- 22:18Broken Strategies
- 25:46Late Adoption
- 32:28Back to the roots
related talks
27mThe curious case of the DevOps engineer and other things ...
33mDevOps and the Rebirth of Childhood Innocence
14mNaked Nerd Interview
26mThe Modern Full-Stack: Owning Your Deployment Pipeline
39mPlatform Engineering as a (Community) Service
26mThe Timeless way of DevOps
32mLooking Back At 13 Years Of DevOps
44mDevOps for developers (or maybe against them?!)