3 ms·
Everywhere I've worked has had on call rotations. Literally everywhere. Nowhere have devs been the first line of support (i.e., not "instead of" per the parent
by lostcolony 4y ago
Everywhere I've worked has had on call rotations. Literally everywhere. Nowhere have devs been the first line of support (i.e., not "instead of" per the parent post, but "as well as"), but they've been in the mix.
Quite frankly, I wouldn't want to work somewhere that didn't. I have a huge problem with the idea of "my team wrote the code, and now isn't responsible for it". I intentionally optimize against "avoid 2 AM pages", and that ensures I push for enough testing and such to avoid them. If it was "someone else's problem", the only pressure I'd be under is to deliver ASAP, and that's unhealthy.
- wnolens 4y agoIt all makes sense and I don't have much in the way of an argument against it fundamentally. But it does make this career path rather miserable to me.
- lostcolony 4y agoWell...I also have not worked anywhere that you personally got paged more than maybe once or twice a year, and that any after hour pages led to the expectation you'd take twice that amount of time off the next day, and if it was more than a couple hours, or interrupted your sleep, you'd take the full day off. And those were not FAANG. So I think it's also the culture and expectations, and it's not ludicrously impossible to get. It just requires, getting back to the topic, a reasonable manager who understands the negative effects of getting paged.