Mechanical rules are never a substitute for clarity of thought.
Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it.
Do what you think is interesting, do something that you think is fun and worthwhile, because otherwise you won’t do it well anyway.
Controlling complexity is the essence of computer programming.
Each new user of a new system uncovers a new class of bugs.
Believe the terrain, not the map.
90% of the functionality delivered now is better than 100% delivered never.
The most effective debugging tool is still careful thought, coupled with judiciously placed print statements.
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.
Trying to outsmart a compiler defeats much of the purpose of using one.
C is a razor-sharp tool, with which one can create an elegant and efficient program or a bloody mess.
Get the weirdnesses into the data where you can manipulate them easily, and the regularity into the code because regular code is a lot easier to work with.
An effective way to test code is to exercise it at its natural boundaries.
If you’re as clever as you can be when you write it, how will you ever debug it?
Don’t document bad code – rewrite it.
Trivia rarely affect efficiency. Are all the machinations worth it, when their primary effect is to make the code less readable?