Bug fixing and reparations

Bug fixing and reparations
Originally it is insect related word - "BUG" also refers to defects and imperfections.

In our artificial world "bug" is applied to any glitch, like sludge in lubricating oil, or a tiny part whose small failure can stop a huge machine.
Murphy's Law works the same way in nature. Like collection of lipids (fatty acids) provoke the interruption of blood supply to part of the heart can cause myocardial infarction, i.e. heart attack, or scrambled DNA sequence that cause an organism to malfunction or die.

Murphy's Laws of Computer Programming & Bugs
1. A working program is one that has only unobserved bugs.
2. If such a program has not crashed yet, it is waiting for a critical moment before it crashes.
3. Software bugs are impossible to detect by anybody except the end user.
4. A failure in a device will never appear until it has passed final inspection.
5. Computers don't make errors-What they do they do on purpose. by Terry Jaster
6. A program that compile on the first run has an error in the algorithm by Iavor Dimitrov
7. Program complexity grows until it exceeds the capability of the programmer who must maintain it.

8. Debugging is at least twice as hard as writing the program in the first place.
So if your code is as clever as you can possibly make it, then by definition you're not smart enough to debug it.
Sent by Brian Kernighan

11. Crab walking syndrome during development - One step forward and two backward.
Bugs will appear in one part of a working program when another 'unrelated' part is modified.
12. The subtlest bugs cause the greatest damage and problems.
- Corollary - A subtle bug will modify storage thereby masquerading as some other problem.

15. Undetectable errors are infinite in variety, in contrast to detectable errors, which by definition are limited.
16. A program generator (i.e. compiler/interpreter) creates programs that are more buggy than the program generator.

17. Gumption's Law (sent by Ray Geist who found it handy when he was debugging computer code.)
Any problem, no matter how complex, can be found by simple inspection performed by non-expert. 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.
Corollary: A nagging intruder with unsought advice will spot it immediately.


56. Every non-trivial program contains at least one bug.
Corollary 1 - A sufficient condition for program triviality is that it have no bugs.
Corollary 2 - At least one bug will be observed after the author leaves the organization.
Corollary 3 - Every non-trivial program can be simplified by at least one line of code. sent by Brandon Aiken



83. A program is good when it's bug free - which is impossible. by Hans van Rijsse

82. Failure is not an option, it's included with the software. by Paul

85. It's not a bug, it's an undocumented feature.

90. Bugs mysteriously appear when you say, "Watch this!"
corollary: If you call another programmer over to see if he knows what's wrong the bug disappears. by S. Bussell.

91. The probability of bugs appearing is directly proportional to the number and importance of people watching. by Bill Smith.

94. If a project is completed on schedule, it wasn't debugged properly.

96. The worst bugs in your program will show up only during the final review.


SIDE EFFECTS & BLAME
---------------------------
16. A hardware failure will cause system software to crash, and the customer engineer will blame the programmer.
17. A system software crash will cause hardware to act strangely and the programmers will blame the customer engineer.
19. Adding manpower to a late software project makes it later.
20. Make it possible for programmers to write programs in English, and you will find that programmers can not write in English.
111. You will always discover errors in your work after you have printed/submitted it.
by Niels Hageman



reference:

Murphy's computers laws