News for hackers. Stuff that matters.
Re:Building an in-house on-call training program for your SR... by dopylitty on Friday February 10, 2023 @10:20AM (#34740748)
Exactly this. On call is an abusive practice. If you think your service should be up 24/7 then pay people to be online to take care of it 24/7.

Forcing people to sit by their phones/computers 24/7 unpaid waiting for a system to maybe have a problem should be a practice explicitly barred by the FLSA.

Re:Building an in-house on-call training program for your SR... by makestuff on Friday February 10, 2023 @10:31AM (#34740913)
Yeah IMO you either use a follow-the-sun rotation and have staff in multiple parts of the world, hire a dedicated nightshift, or pay OT.

If the SRE is unable to solve the issue and needs to page the escalation engineer they should get OT for that if it outside business hours. The whole "oh you got woken up at 3am just log in late" is BS because I still have the same amount of work to do.

Re:Building an in-house on-call training program for your SR... by olvy0 on Friday February 10, 2023 @10:27AM (#34740867)
Completely agree. My team has on-call duty, but we don't have to do it 24/7, just during business hours. I hope we never get to the point where we're giving support 24/7.

Slightly off topic: stdout's On-Call.

https://www.youtube.com/watch?v=OiApm-OFfsY

Re:Building an in-house on-call training program for your SR... by dangerwill on Friday February 10, 2023 @02:10PM (#34744228)
Yeah I went from a job where being oncall meant a LOT of pages but the oncall rota was a follow the sun model and so the oncall shifts just ended up being normal work days where you were just 100% interrupted constantly. I thought this was hell but now that I work at a company with 72 hour long oncall shifts, even though the after-hours page rate is very low (once a month or so), the "always on" feeling is even worse.

I am constantly thinking about how abusive this practice is