Dev/Ops relationships, status: It's Complicated
summary
Starts in an era where devs email packages to ops and lack production access, CI is absent and QA environments differ wildly, then shifts to team‑managed infrastructure where developers inherit production credentials and a 24/7 pager. A recurring surprise: a monthly billing run broken by a carriage return forces a midnight live SQL edit on production with no backups before running SQL. Outcome forces changes: better monitoring, logging, alerting and documentation, shared pager rotations, and more mutual empathy.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 4:26Whats inside the package
- 6:12Team managed infrastructure
- 8:48Volunteering
- 9:36Billing run
- 12:05Troubleshooting
- 15:15Conclusion
related talks
34mFrom Dev to DevOps
43mDevOps – when doing the right thing hurts!
34mDevops or: How I Learned to Stop Worrying and Love the Ops Team
30mWhat's It Like When DevOps Is Just Another Day at the Office?
24mWar Stories About the Ops in DevOps
55mDevOps @Scale (Greek Tragedy in 3 Acts)
58mDevOps @ Scale — Greek Tragedy in Three Acts
36mDevOps in Outsource… Really!