Conference Call Services
Dog Ramps Valentine cards
LaughNet
Gator bar

Subscribe to LaughNet Daily Jokes in Your Mailbox Daily
  Home » Computers »
Search
Search Body
Categories
Aging (14)
Bloopers (19)
Blue Collar (11)
Cartoons (38)
Computers (83)
Crude (42)
Education (58)
Gender (89)
Holiday (36)
How To's (7)
Jokes (45)
Misc. (119)
Parenting (17)
Pets (18)
Photos-> (44)
Politics (22)
Religion (24)
Sci-Fi (8)
Songs (6)
Sports (6)
Tests (16)
Workplace (90)
What's New?
Short Management Courses Part II
A list of redneck computer terms
Short Management Courses



Cardwoo Buy

Murphy's Laws For Programming

 

 1. Any given program, when running, is obsolete.
 2. Any given program costs more and takes longer.
 3. If any program is useful, it will have to be changed.
 4. If a program is useless, it will have to be documented.
 5. Any given program will expand to fill all available memory.
 6. The value of a program is proportional to the weight of its output.
 7. Program complexity always grows until it exceeds the capability of
    the programmer who must maintain it.
 8. If a test installation functions perfectly, all subsequent systems
    will malfunction.
 9. Job control cards that positively cannot be arranged in improper
    order will be.
10. If the input editor has been designed to reject all bad input, an
    ingenious idiot will discover a method to get bad data past it.
11. Profanity is the one language all programmers know best.
12. Adding manpower to a late software project makes it later.
13. A carelessly planned project takes three times longer to complete
    than expected; a carefully planned project takes only twice as long.
14. (Lubarsky's Law of Cybernetic Entomology) There is always one more
    bug.
15. It is impossible to make any program foolproof because fools are
    so ingenious.
16. When things are going well, something will go wrong.
17. When things just can't get any worse, they will.
18. Anytime things appear to be going well, you have overlooked something.
19. Test functions and their tests should be reproducible -- they should
    all fail in the same way.
20. If it looks easy, it's tough.
21. If it looks tough, it's damn near impossible.
22. You always find any bug in the last place you look.
23. Anything can be made to work if you fiddle with it long enough.
24. A terminal usually works better if you plug it in. 25. If all else
    fails, read the documentation.
26. If you do not understand a particular word in a piece of technical
    writing, ignore it. The piece will make perfect sense without it.
27. No matter how much you do, you'll never do enough.
28. What you don't do is always more important than what you do do.
29. Procrastination avoids boredom; one never has the feeling that there
    is nothing important to do.
30. Always leave room to add an explanation if it doesn't work out.
31. No amount of genius can overcome a preoccupation with detail.
32. Nothing is impossible for a man who doesn't have to do it himself.
33. If builders built buildings the way programmers write programs,
    then the first woodpecker than came along would destroy civilization.
34. Programmers will act rational when all other possibilities have
    been exhausted.

 

This article was added to LaughNet on Wednesday 16 March, 2005.


Save Murphy's Laws For Programming to del.icio.us Save to del.icio.us
  |   Digg this Murphy's Laws For Programming Digg this   |   Google Bookmark Murphy's Laws For Programming Google Bookmark this   |   Add Murphy's Laws For Programming to Yahoo myWeb Add to Yahoo

Reviews
Reviews
  Home » Computers »

LaughNet page design is copyright (C) by Stephen Henry and may not be copied . All material is believed to be in the public domain. If an article does not have the appropriate credits please Contact us.