From Dev to DevOps
summary
Developers leave “throw it over the wall” and start running production: they reproduce production with deployable images, discover native dependency failures (ruby gem native builds), learn networking and noisy-neighbor failure modes, and join an on-call rotation so midnight pagers surface real bugs. Teams merge ops work into sprints, remove handoff meetings, and build shared runbooks and dashboards. The result is fewer finger-pointing incidents, faster fixes, and noticeably better production reliability using Google ops ideas.
AI-written summary · about
chapters (5)
- 0:00Start
- 13:51How did it work?
- 16:13Wear seatbelts! Mistakes will be made but you don't want them to affect actual work. You need sane testing environments and automated test suites.
- 20:50Cross team, cross functional, cross whatever No one is alone and moving people around produces better understanding of all the different needs inside a business.
- 30:34Questions?
related talks
42mHow DevOps Accelerates "Idea to Prod" at Google and What It Means to You
30mWhat's It Like When DevOps Is Just Another Day at the Office?
24mHow DevOps changed the way we operate software
19mDev/Ops relationships, status: It's Complicated
34mDevops or: How I Learned to Stop Worrying and Love the Ops Team
31mDevOps for Java Developers (Or Maybe Against Them?!)
34mDevOps: Next
27mDevOps Next