4 ms·
How, pray tell, is someone utterly unfamiliar with a code base supposed to be able to deal with unforeseen issues in production for that service? (Worse, the i
by deathanatos 4y ago
How, pray tell, is someone utterly unfamiliar with a code base supposed to be able to deal with unforeseen issues in production for that service?
(Worse, the incentives for improvements to production quality, and thus on-call quality, are utterly mis-aligned.)
Ironically, I say this as someone presently on-call for a bunch of stuff for which I am utterly unfamiliar with the code base of, and have no time to become familiar with. It's going predictably badly.
- greedo 4y agoOn call isn't about fixing the problem yourself, it's knowing who the right person is to contact when an issue arises.
- deathanatos 4y agoSo just page that person directly (the dev, for the purposes of this argument). (And because I feel like this is bound to draw a strawman, steelman this: while there are definitely pages that might not get routed to BE eng in particular, assume we're routing pages to the person responsible for that system. I.e., in the face of infrastructural problems, those pages get routed to something like "infra eng", although IME there's very little that can be done with those in the middle of the night…)
- andelink 4y agoEhh, if your oncall shift mostly an exercise in reassigning pages, you need to invest more time in proper incident routing