Hacker News new | ask | show | jobs
by Niksko 2456 days ago
This is super interesting. So you had a high number of pages, but then you also had a really clearly defined and sensible sounding way of dealing with the root causes of the pages?

If you're constantly fixing the things causing you to get pages, why are there still many more than one per day? Just prioritisation of other work over fixes?

We have a similar system, though we have one person on after hours support doing normal work during the day, and one person during the day who doesn't do normal work. That person works on remediating the issues that cause people to get paged. Leads to a pretty low number of pages.

1 comments

My rotation was a bit weird. I was on an ops team for a service, but my ops team did not have our own rotation- each of us took part in the various dev team rotations (the theory is nice, the ops team had a deep view of most aspects of the service. I don't think this was common to other service teams). The dev team I took part in was an absolute trainwreck. Poorly managed at the team level and one level above (the owners/managers of the service). More concerned with getting features out and burning through people to make progress. The issues were always brought up and root-caused properly, but poor architecture led to a lot of "well, we can't do that until x happens". I should reiterate that I'm no longer at the company - definitely wasn't the place for me (and my sanity)!