4 ms·
Wow. For a lot of ops jobs, there is scheduled off-hours work (i.e. we need to upgrade servers when it won't affect customers) and unscheduled (oh shit, a redu
by rdl 16y ago
Wow.
For a lot of ops jobs, there is scheduled off-hours work (i.e. we need to upgrade servers when it won't affect customers) and unscheduled (oh shit, a redundant system wasn't).
I generally find the best way to deal with this is flexible comp time, vs. cash, and making sure it doesn't become too much difficulty for ops people. For instance "oh, you got paged last night and worked really late? Come in (or call in) late tomorrow so we can have the post-incident meeting, and then take another day off later this week", but in general just using flexibility to figure out what people want (if someone had to come in and it ruined a dinner with SO, I'd probably encourage expensing a replacement date/meal; other people might prefer a comp day or a new 30" monitor. I'd personally want "actually fix whatever broke so I don't get paged for the same reason again..."; the most demoralizing ops calls are when the same thing happens over and over again and it still doesn't get fixed)
There's also a great tradition from the military of the most senior people taking over junior jobs (gate security, food service) on major holidays, to give the other people a break. I actually like working xmas to new years, inclusive, because I end up getting a lot more work done in that week than in any other month.