I'm replying to the post saying this is an "industry standard" thing--I'm not saying that there is no disaster scenario ever. Obviously not every contingency ca

I'm replying to the post saying this is an "industry standard" thing--I'm not saying that there is no disaster scenario ever. Obviously not every contingency can be planned. However, there are certainly signals that a company respects a developers' time. Things like...was there effort put in the product around things that might minimize developer on-call time, like having more user self-serve options, or spending more time on testing, or having a proper feedback loop for recurring issues to be permanently squashes in a timely fashion, etc etc. Are managers regularly a part of these off-hour on-call issues so they're affected too, thus motivated to resolve it? Or does the company just abusively unload all of the burden on the developer and force them to use up their own personal time to maintain a product? Far too often it's the latter, and I think it should be clear to all that this is abusive practice and not "normal" or "standard" nor should any of us consider it that way.