All I need to know about DevOps I learned from XKCD
summary
Claims that XKCD maps recurring DevOps realities: expect failures like left-pad removal, prioritize developer productivity over maintaining tools, and plan for dependencies breaking. Offers concrete examples: an actual 11-page Word document that instructs which JARs to copy for deployment, an engineer literally fixing Redmine with a screwdriver, and the existence of a web-based xkcd terminal that demonstrates playful tooling. Argues tool consolidation into platforms replaces stitching many point tools.
AI-written summary · about
chapters (8)
- 0:00Intro
- 0:41A new perspective
- 1:47Outside the box
- 2:15Fake it
- 2:36Everyone has processes
- 2:52You never really have DevOps
- 3:14Developer productivity
- 4:31Conclusion
related talks
34mDevops or: How I Learned to Stop Worrying and Love the Ops Team
44mDevOps for developers (or maybe against them?!)
25mDeveloper Experience is central to DevOps success
27mThe curious case of the DevOps engineer and other things ...
48mThe Unix Way Seen by a DevOps
33mDevOps and the Rebirth of Childhood Innocence
45mDevops for Dummies^WDeveloper
25mDevOps: Why do we Keep Messing Up?
