Murphy's Law for Software Releases

As a release manager, I'm working on a theory about Murphy's law as it applies to engineering process in tech companies. It never fails... whatever can go wrong, does go wrong. Here's my theory (drawn off of stressful personal experiences) so far:

On the deadline...

- hardware fails
- files in the build become mysteriously empty
- QA engineers get sick
- long-running bugs appear
- you make procedural mistakes in the middle of 3-hour long procedures
- developers randomly check in new code
- developers forget to check in critical code
- post-work plans die