3 ms·
My last gig, on call worked well, I thought, for a few reasons: it was our services that we wrote, it was 1 wk out of 6 that you were on call, we heavily priori
by sethammons 4y ago
My last gig, on call worked well, I thought, for a few reasons: it was our services that we wrote, it was 1 wk out of 6 that you were on call, we heavily prioritized fixing unactionable alerts and automating fixes -- every alert had a runbook entry that described the non-automated fixes, and while on call your or sprint commitments were not counted,
That last point was very nice as it meant you could work on whatever you felt was most important for quality of life improvements all week long while not fielding on call issues. This meant that I looked forward to on call.
- chitowneats 4y agoI love that last point. I will be pushing for this now given any opportunity.
- ozim 4y agoIt is OK being on call on your servers and your software. I think it is also why less and less people having stuff on premise and going for SaaS/Cloud solutions. If someone wants to have my software on their servers and me not having any access better they have dedicated person for running it and I don't care even if they pay $1000 per hour - I am still not dealing with server I don't know talking on the phone with admin that has no clue how my software should be configured.
- dllthomas 4y agoI'd do it for $1000/hr, but not for more than 8 hours a week.
- bogomipz 4y ago>"My last gig, on call worked well, I thought, for a few reasons: it was our services that we wrote, it was 1 wk out of 6 that you were on call, ..." Am I the only one that thinks the prospect being on call one week every six is horrifying?
- mcronce 4y agoHonestly, that last point seems like something that would make on-call extremely palatable. Essentially acknowledging "on-call sucks; in return, here's the latitude to work on whatever you happen to think is important/interesting"