If you're as clever as you can be when you write it, how will you ever debug it?

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

90% of the functionality delivered now is better than 100% delivered never.

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.

Don't document bad code - rewrite it.

Believe the terrain, not the map

Trivia rarely affect efficiency. Are all the machinations worth it, when their primary effect is to make the code less readable?