Interesting programing laws.
Bove's Theoremthe Remaining Work to Finish in Order To Reach Your Goal Increases As The Deadline Approaches.
Brook's lawadding manpower to a late software project makes it lat.
Cann's Axiomwhen All else fails, read the instructions.
Deadline-Dan's Demonevery Task Takes Twice As Long As you think it will take it. If youdouble the time you think it will time, IT Will Actually Take Four Times as long.
Demian's ObservationThere Is Always One Item On The Screen Menu That Is Mislabeled andShould Read "Abandon Hope All ye Who Enter He"
Dr. Caligari's Come-Backa Bad Sector Disk Error Occurs Only After You've Done Several Hoursof Work without Performing A Backup.
FINAGLE's Rules:
To study an application best, understand it thoroughly before youstart. Always keep a record of data. It indicates you've been working. Always draw your curves, then plot the reading. In case of doubt, make it sound convincing. Program results should Always Be Reproducible. They Should Allfail in The Same Way. Do Not Believe In Miracles. Rely on Them.
Franklin's ruleblessed is the end, for he / she will not bedisappointed.
Gilb's Law of Unreliability
At the source of every error which is blamed on the computer youwill find at least two human errors, including the error of blamingit on the computer. Any system which depends on human reliability is unreliable. Undetectable errors are infinite in variety, in contrast todetectable errors Which by Definition Are Limited. Investment in Reliability Will Investment Until It Exceeds Theprobable Cost of Errors, or Until Someone INSISTS ON GETTINGSOME USEFUL WORK DONE.
Gummidge's LawThe amount of expertise varies in inverse proportion to the numberof statements understood by the general public.Harp's Corollary to Estridge's LawYour "IBM PC-compatible" computer grows more incompatible with everypassing moment.
Heller's Lawthe First Myth of Management Is That IT EXISTS.
Hind's Law of Computer Programming
Any given program, when running, is obsolete. If a program is useful, it will have to be changed. If a program is useless, it will have to be documented. Any given program will expand to fill all available memory. The value of a program is proportional to the weight of itsoutput. Program complexity grows until it exceeds the capability of theprogrammer who must maintain it. Make it possible for programmers to write programs in English, and you will find that programmers can not write in English.
Hoare's Law of Large ProgramsInde Large Program Is A Small Program Strugging To Get Out.
The Last One's Law of Program Generator Creates Programs That Are More "Buggy" Than Theprogram Generator.
Meskimen's Lawthere's Never Time To Do It Right, But Always Time To Do It Over.
.
Murphy's law of thermynamics.things get Worse under.
.
.
Nolan's Placeboan Ounce of Image Is Worth A Pound of Performance.osborn's Lawvariables Won't constants aren't.
O'TOole's Commentary ON Murphy's Lawmurphy Was An Optimist.
Peer's Lawthe Solution To a Problem Changes The Problem.
Rhode's Corollary to Hoare's LawInside Every Complex and Unworkable Program Is A Useful Routinestruggling To to Be Free.
.
Sattinger's Lawit Works Better if You Plug It in.
Shaw's PrinciPleBuild A System That Even A Fool Can Use, And Only A Fool Will Want Touse IT.
Snafu Equations
Given any problem containing N equations, there will be N 1 unknown. An object or bit of information most needed will be leastavailable. Any device requiring service or adjustment will be leastaccessable. Interchangeable device's will not. In any human endeavor, once you Have Exhausted All Possibilities and Fail, There Will Be One Solution, Simple and Obvious, Highly VisibleTo Everyone else. Badness comes in Waves.
Thoreau's Theories of Adaptation
After months of training and you finally understand all of a program's commands, a revised version of the program arrives with an all-new command structure. After designing a useful routine that gets around a familiar "bug" in the system, the system is revised , the "bug" is taken away, andyou're left with a useless routine. Efforts in improving a program's "user friendliness" invariablylead to work in improving user's "computer literacy." that's not a "bug," that's a feature!
Weinberg's CorollaryAn expert is a person who avoids the small errors while sweeping onto the grand fallacy.Wood's AxiomAs soon as a still-to-be-finished computer task becomes a life-or-deathsituation, the power fails.
Zymurgy's First Law of Evolving System Dynamicsonce You Open a CAN of Worms, The Only Way To Recan The To Usea Larger CAN.
