Buttered Toast Wiki

Wisdom by Peck

Peck

12 pieces of wisdom

In any program, any error which can creep in will eventually do so.

First Peck's Programming PostulatePostulate

Not until the program has been in production for at least six months will the most harmful error be discovered.

Second Peck's Programming PostulatePostulate

Any constants, limits, or timing formulas that appear in the computer manufacturer's literature should be treated as variables.

Third Peck's Programming PostulatePostulate

The most vital parameter in any subroutine stands the greatest chance of being left out of the calling sequence.

Fourth Peck's Programming PostulatePostulate

If only one compiler can be secured for a piece of hardware, the compilation times will be exorbitant.

Fifth Peck's Programming PostulatePostulate

If a test installation functions perfectly, all subsequent systems will malfunction.

Sixth Peck's Programming PostulatePostulate

Job control cards that positively cannot be arranged in improper order, will be.

Seventh Peck's Programming PostulatePostulate

Interchangeable tapes won't.

Eighth Peck's Programming PostulatePostulate

If more than one person has programmed a malfunctioning routine, no one is at fault.

Ninth Peck's Programming PostulatePostulate

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.

Tenth Peck's Programming PostulatePostulate

Duplicated object decks which test in identical fashion will not give identical results at remote sites.

Eleventh Peck's Programming PostulatePostulate

Manufacturer's hardware and software support ceases with payment for the computer.

Twelfth Peck's Programming PostulatePostulate