Hacker News new | ask | show | jobs
by brudgers 639 days ago
The best way to manage on-call is to not have on-call. On-call means the organization is understaffed. Hiring new positions to handle off hours, will solve the problem. Good luck.
5 comments

I’ve seen this comment or similar many times on HN, and I wonder if it’s a result of the kinds of companies people work for.

If you’re in a “boring” industry, it’s completely infeasible to hire a 24/7 dev team just to cover on-call. Doubly so if on-call requires physical access or security clearance.

If you’re at some multinational big tech firm, sure, I can see how it makes sense to geographically distribute the team so that there’s no “out of hours” support. For the rest of the industry it’s a non-starter.

On the other hand, a "boring" industry doesn't generate 4-5 on call events per week for just one team.
Or alternatively just shut down at 5 like a normal business. Can't be open 24/7 without fully staffing 24/7.
Realistically, lots of parts of capitalism never sleep, and having outages at night still costs lots of money, astronomical amounts if there was no one there to fix it.
If you are open 24/7 you should be staffed 24/7.

They are not "no-call" they are the night shift.

This. Even Burger joints have shifts so that they are operational 24/7.
Hardly any of them anymore since the pandemic. Our local McDonald's used to be 24x7 now they close at 2200. Nobody will work later than that anymore, at least not for a wage that can be covered by the amount of sales at those hours.
I came here to say this but for a different reason.

Have a mature enough development process and pipeline that production deployments are repeatable and predictable at any time.

Bake testing into the procedure.

What about weekends?