4 ms·
No, because in that case you are responsible for other people's systems you have no idea about and there is no incentive to fix them. I am always on call to se
by throwaway55421 5y ago
No, because in that case you are responsible for other people's systems you have no idea about and there is no incentive to fix them.
I am always on call to secure my own house, so I have a good alarm system, cameras, locks etc which means I hopefully don't have to do much. It doesn't keep me up at night when I'm on holiday because, well, it's overwhelmingly likely that nothing will happen.
If I were on call for the neighbourhood or general area once a week, I'd probably have to physically be there patrolling it because otherwise I have liability for things which are outside of my control.
- maximus-decimus 5y agoAnd if somebody ever leaves the company for any reason, who is on call for their stuff?
- throwaway55421 5y agoProjects get reassigned over time regardless. It's not as if this is some strict 1:1 relationship, we obviously had more than 1 person with knowledge of / working on a codebase. It would have been an issue if 2-3 working on the same thing left simultaneously, but for more reasons than just on-call.
- maximus-decimus 5y agomaybe there is a big difference between my workplace and yours, but for me a lot of stuff never gets improved much after it's written so it's basically impossible to get up to speed until the person who owned it leaves the company and now you're she one fixing their bugs. Onboarding is just really hard on legacy projects.