3 ms·
>1. Whoever is on call, their job isn't only to answer pages, but also to improve the system Way to make being on-call more punishing as well as detract from b
by bobkazamakis 4y ago
>1. Whoever is on call, their job isn't only to answer pages, but also to improve the system
Way to make being on-call more punishing as well as detract from both goals -- your clients receive worse support and the amount of work done on the fix is inversely proportional to the time you're spending with clients who are calling you because there is a problem, not because they just want to talk.
2 actually works; tech debt hackathons are a great thing, and sometimes ops and dev hands don't communicate as effectively as they need to throughout the SDLC.
- angarg12 4y agoThe point of 1 is that whoever is oncall shouldn't be working on features/sprint tasks, but actually fixing the underlying problems of the system. This is second to addressing the pages. Of course if your system is so deficient that engineers spend 100% of their time putting out fires, then you need to address that first. That's what reducing toil from the SRE books is about.