Strange Computer Science Laws

by on March 23rd, 2008

Here are some very very interesting laws related to computer sciences subject and work. These will also give you some precautions, instructions and pieces of advice which probably you will need in case you are a computer science student or worker.

  • The remaining work to finish in order to reach your goal increases as the deadline approaches.
  • Adding manpower to a late software project makes it later.
  • When all else fails, read the instructions.
  • A bad sector disk error occurs only after you’ve done several hours of work without performing a backup.
  • To study an application best, understand it thoroughly before you start.
  • Always keep a record of data. It indicates you’ve been working.
  • In case of doubt, make it sound convincing.
  • Do not believe in miracles. Rely on them.
  • Blessed is the end user who expects nothing, for he/she will not be disappointed.
  • 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.
  • The first myth of IT Management is that it exists.
  • 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.
  • 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.
  • Inside every large program is a small program struggling to get out.
  • A program generator creates programs that are more “buggy” than the program generator.
  • There’s never time to do it right, but always time to do it over.
  • Things get worse under pressure.
  • The first ninety percent of the task takes ninety percent of the time, and the last ten percent takes the other ninety percent.
  • The man who can smile when things go wrong has thought of someone he can blame it on.
  • An ounce of image is worth a pound of performance.
  • The solution to a problem changes the problem.
  • Judgement comes from experience; experience comes from poor judgement.
  • It works better if you plug it in.
  • Build a system that even a fool can use, and only a fool will want to use it.
  • 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 accessible.
  • 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.
  • An expert is a person who avoids the small errors while sweeping on to the grand fallacy.
  • As soon as a still-to-be-finished computer task becomes a life-or-death situation, the power fails.