Murphy’s Laws for Software Engineers

1. The bug you can’t find is the one causing the problem.
2. The more critical the bug, the harder it is to reproduce.
3. Code will compile perfectly until the demo starts.
4. The likelihood of a feature request is directly proportional to how difficult it is to implement.
5. If everything seems to be going well, you have definitely overlooked something.
6. The one piece of hardware you need for testing will be the one that fails.
7. The moment you fix one bug, three more will appear.
8. The user never uses the software the way you intended.
9. When all else fails, blame the network.
10. There is always one more bug.
11. Your most carefully written comment will be misinterpreted by someone else.
12. The best code is the code you never have to touch again.
13. The chance of the server going down is directly proportional to the importance of the project.
14. The simplest features will have the most complicated bugs.
15. The user is always right, except when they are wrong.
16. Debugging is harder than writing the code right in the first place.
17. A feature is only considered complete after it has been rewritten at least three times.
18. The more urgent the deadline, the higher the likelihood of a major outage.
19. Users don’t know what they want until you deliver exactly what they asked for.
20. The best documentation is the code itself, which no one reads.
21. Every program has at least one bug and can be shortened by at least one line of code.
22. The probability of a typo in the code increases with the length of the meeting discussing the bug.
23. A program that compiles is a program that will soon be obsolete.
24. The moment you declare your code is bug-free, a new bug will be discovered.
25. The easier it is to make a change, the harder it is to change it back.
26. If it works in development, it won’t work in production.
27. Any code that has not been tested will contain errors.
28. The fastest way to find a bug is to tell the team there are no bugs left.
29. The likelihood of an error occurring is directly proportional to the time since the last backup.
30. If the code runs on the first try, something is terribly wrong.

These aren’t original. Just collective knowledge scattered around the internet.