Murphy's Computer Law + others

王朝other·作者佚名  2006-01-08
窄屏简体版  字體: |||超大  

Interesting programming laws.

Bove's Theorem

The remaining work to finish in order to reach your goal increases as

the deadline approaches.

Brook's Law

Adding manpower to a late software project makes it later.

Cann's Axiom

When all else fails, read the instructions.

Deadline-Dan's Demon

Every task takes twice as long as you think it will take. If you

double the time you think it will take, it will actually take four

times as long.

Demian's Observation

There is always one item on the screen menu that is mislabeled and

should read "ABANDON HOPE ALL YE WHO ENTER HERE."

Dr. Caligari's Come-Back

A bad sector disk error occurs only after you've done several hours

of work without performing a backup.

Finagle's Rules:

To study an application best, understand it thoroughly before you

start.

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 all

fail in the same way.

Do not believe in miracles. Rely on them.

Franklin's Rule

Blessed is the end user who expects nothing, for he/she will not be

disappointed.

Gilb's Law of Unreliability

At the source of every error which is blamed on the computer you

will find at least two human errors, including the error of blaming

it on the computer.

Any system which depends on human reliability is unreliable.

Undetectable errors are infinite in variety, in contrast to

detectable errors, which by definition are limited.

Investment in reliability will increase until it exceeds the

probable cost of errors, or until someone insists on getting

some useful work done.

Gummidge's Law

The amount of expertise varies in inverse proportion to the number

of statements understood by the general public.

Harp's Corollary to Estridge's Law

Your "IBM PC-compatible" computer grows more incompatible with every

passing moment.

Heller's Law

The 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 its

output.

Program complexity grows until it exceeds the capability of the

programmer who must maintain it.

Make it possible for programmers to write programs in English,

and you will find that programmers cannot write in English.

Hoare's Law of Large Programs

Inside every large program is a small program struggling to get out.

The Last One's Law of Program Generators

A program generator creates programs that are more "buggy" than the

program generator.

Meskimen's Law

There's never time to do it right, but always time to do it over.

Murphy's Fourth Law

If there is a possibility of several things going wrong, the one

that will cause the most damage will be the one to go wrong.

Murphy's Law of Thermodynamics.

Things get worse under pressure.

Ninety-Ninety Rule of Project Schedule

The first ninety percent of the task takes ninety percent of the

time, and the last ten percent takes the other ninety percent.

Nixon's Theorem

The man who can smile when things go wrong has thought of someone

he can blame it on.

Nolan's Placebo

An ounce of image is worth a pound of performance.

Osborn's Law

Variables won't constants aren't.

O'Toole's Commentary on Murphy's Law

Murphy was an optimist.

Peer's Law

The solution to a problem changes the problem.

Rhode's Corollary to Hoare's Law

Inside every complex and unworkable program is a useful routine

struggling to to be free.

Robert E. Lee's Truce

Judgement comes from experience; experience comes from poor judgement.

Sattinger's Law

It works better if you plug it in.

Shaw's Principle

Build a system that even a fool can use, and only a fool will want to

use 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 least

available.

Any device requiring service or adjustment will be least

accessable.

Interchangeable device's won't.

In any human endeavor, once you have exhausted all possibilities

and fail, there will be one solution, simple and obvious, highly visible

to 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, and

you're left with a useless routine.

Efforts in improving a program's "user friendliness" invariably

lead to work in improving user's "computer literacy."

That's not a "bug," that's a feature!

Weinberg's Corollary

An expert is a person who avoids the small errors while sweeping on

to the grand fallacy.

Wood's Axiom

As soon as a still-to-be-finished computer task becomes a life-or-death

situation, the power fails.

Zymurgy's First Law of Evolving System Dynamics

Once you open a can of worms, the only way to recan them is to use

a larger can.

 
 
 
免责声明:本文为网络用户发布,其观点仅代表作者个人观点,与本站无关,本站仅提供信息存储服务。文中陈述内容未经本站证实,其真实性、完整性、及时性本站不作任何保证或承诺,请读者仅作参考,并请自行核实相关内容。
 
 
© 2005- 王朝網路 版權所有 導航