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

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.)

Mechanical rules are never a substitute for clarity of thought.

C is a razor-sharp tool, with which one can create an elegant and efficient program or a bloody mess.

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

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

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