Drott's Programming Laws

The Laws of Programming

by M. Carl Drott

The Law of the Run Imperative
If it doesn't run now, it doesn't run.

The Law of Theft
The only truly original algorithms were by John VonNeuman, and he was a time traveler who stole them from the future.

The Law of Programmer Control
Nothing, absolutely nothing, should happen that is not under programmer contro

The Law of Warm Oatmeal
Any section of code longer than 26 statements causes the programmer's brain to turn to mush.

The Law of Detail
Nothing is so simple that there is not a stupid way to do it.

The Law of Simplicity
Honor the Law of Brevity except when you shouldn't.

The Law of Brevity
This is no excuse to violate the Law of Simplicity.

The Law of Best Language
Thought takes place in human languages, and thought always takes precedence.

The Law of Understanding
If you don't know what is supposed to be happening, it won't.

The Law of Sweat
The ease of use of a program is directly proportional to how hard the programmer works (and conversely.)

The Law of the Failed Demo
Every user is a deranged psychopath who is specifically out to get YOU.

The Law of Change
Every program has to be changer sooner or later, in fact every program has to be changed sooner AND later.

The Law of Modification
If you didn't write the program to be modified, it can't be.

The Potato Chip Law
The better the program, the more it will make the user want a better program.

The Law of Documentation
There is never any "after" in which to write documentation.

The Law of Storage
If you don't run out of disk space then you WILL run out of memory - and conversely.

The Law of Method
Against stupidity, every program development methodology is in vain.

this page is at http://drott.cis.drexel.edu/ProgLaws.htm