Loosing Control and Being OK With It
summary
Claim: embracing shared responsibility reduces outages because ops cannot see or control everything and developers push at 2 a.m. Concrete work includes building configuration management, scripting and online integration systems to automate recovery, plus explicit runbooks and a recovery plan. Testing across QA, unit tests and a stage environment plus rollback tooling prove outability. Result: automation lets anyone execute a safe deploy — e g a big red button or Slack command that actually restores service.
AI-written summary · about
related talks
26mMission Critical Mindset Building a Culture of Resilience in DevOps Teams
02mOpening Remarks
37mCoordination
44mDeveloping a Culture of Reliability and Resilience through Chaos
47mWhere the Security Rubber Meets the DevOps Road
43mBetter Software Development Systems through Stress
01h 39mPostOps: A Non-Surgical Tale of Software, Fragility, and Reliability
50mDevOps Project Failures - Lessons Learned and Strategies for Recovery