Each new user of a new system uncovers a new class of bugs.

Some compilers allow a check during execution that subscripts do not exceed array dimensions. This is a help, but not sufficient. First, many programmers do not use such compilers because They're not efficient. (Presumably, this means that it is vital to get the wrong answers quickly.)

Trying to outsmart a compiler defeats much of the purpose of using one.

As we said in the preface to the first edition, C "wears well as one's experience with it grows." With a decade more experience, we still feel that way.

If you had done something twice, you are likely to do it again.

The most effective debugging tool is still careful thought, coupled with judiciously placed print statements.

An effective way to test code is to exercise it at its natural boundaries