It shouldn't be. I mean, things go wrong. It's the one universal truth of any engineering process. Finding out why the thing that went wrong went wrong, and ma

It shouldn't be. I mean, things go wrong. It's the one universal truth of any engineering process. Finding out why the thing that went wrong went wrong, and making sure that it doesn't go wrong in the future is just part of the job. I work on an on-call rotation --- it's not as exciting as rocket science, which is both unfortunate and fortunate --- and yes, things go wrong; and one of the biggest rules of our process for when things do go wrong is 'Is it the end of your shift? Then hand off and go home. NO THIS IS NOT NEGOTIABLE.' If the process itself is unable to cope smoothly with something going wrong, then the process has gone wrong. (And someone should find out why it went wrong, and make sure that it doesn't go wrong in the future.)