|
|
|
|
|
by curryst
2206 days ago
|
|
I'm not a manager, but my managers are typically available by phone for "oh shit" situations. I say typically in the sense that they keep their phone around, and will answer if it goes off, but don't make a promise that they will have cell service, etc. That is with the explicit warning that it is only to be used in situations where the site is down and we've called everyone else. Whether they answer email is hit or miss. The ones that do I think are just workaholics. My take is that I don't generally mind, because typically the reason I'm getting called is that I dropped the ball on something. I've been called twice out of work hours when I wasn't on call. Once because I developed a system and did a shitty job training other people on it, so when something broke that wasn't a simple fix, I got called. The other time was because the solo dev for the product was on vacation, his replacement on call didn't know much about the system, and I had worked with it the most other than the main dev. I should have documented how I worked with the system and fixed it in the past, but I didn't, because documentation always ends up as the last thing I want to do. The org likes documentation and would have given me time to do it, I just didn't want to. So I reaped what I sowed there. |
|