As leis de Murphy

1. Any given program, when running, is obsolete.
2. If a program is useless, it will have to be documented.
3. Program complexity grows until it exceeds the capability of the programmer who must maintain it.
4. Bugs will appear in one part of a working program when another 'unrelated' part is modified.
5. The subtlest bugs cause the greatest damage and problems.
6. A hardware failure will cause system software to crash, and the customer engineer will blame the programmer.
7. A system software crash will cause hardware to act strangely and the programmers will blame the customer engineer.
8. Undetectable errors are infinite in variety, in contrast to detectable errors, which by definition are limited.
9. Adding manpower to a late software project makes it later.
10. The probability of a hardware failure disappearing is inversely proportional to the distance between the computer and the customer engineer.
11. Bugs are impossible to detect by anybody except the end user.
12. A failure in a device will never appear until it has passed final inspection.
13. The hard drive on your computer will only crash when it contains vital information that has not been backed up.
14. Computers don't make errors.What they do they do on purpose.
15. An expert is someone brought in at the last minute to share the blame.
16. For any given software, the moment you manage to master it, a new version appears. The new version always manages to change the one feature you need most.
17. Most computer errors can be attributed to a similar problem - a screw loose behind the keyboard.
18. A patch is a piece of software which replaces old bugs with new bugs.
19. The chances of a program doing what it's supposed to do is inversely proportional to the number of lines of code used to write it.
20. It's not a bug, it's an undocumented feature.
21. The only thing worse than an end-user without a clue is an end-user who has a clue - usually the wrong one.
22. The probability of bugs appearing is directly proportional to the number and importance of people watching.
23. If a project is completed on schedule, it wasn't debugged properly.
24. The worst bugs in your program will show up only during the final review.
25. The likelihood of problems occurring is inversely proportional to the amount of time remaining before the deadline.
26. After a software is released, the first bug found will be by a person who normally does not use that portion of the program but was wondering why he can't do something he normally would not do.
27. The troubleshooting guide contains the answer to every problem except yours.
28. The problem always exists between one keyboard and it's respective chair.
29. A computer is only as smart as the person using it
30. Every solution breeds new problems.
31. Logic is a systematic method of coming to the wrong conclusion with confidence.
32. If builders built buildings the way programmers wrote programs, then the first woodpecker that came along would destroy civilization.
33. Work expands to fill the time available for its completion.