Another effective [debugging] technique is to explain your code to someone else. This will often cause you to explain the bug to… — Brian Kernighan Copy Share Image
Get the weirdnesses into the data where you can manipulate them easily, and the regularity into the code because regular code is a lot… — Brian Kernighan Copy Share Image
Trying to outsmart a compiler defeats much of the purpose of using one. — Brian Kernighan Copy Share Image
An effective way to test code is to exercise it at its natural boundaries — Brian Kernighan Copy Share Image
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,… — Brian Kernighan Copy Share Image
Trivia rarely affect efficiency. Are all the machinations worth it, when their primary effect is to make the code less readable? — Brian Kernighan Copy Share Image
C is a razor-sharp tool, with which one can create an elegant and efficient program or a bloody mess. — Brian Kernighan Copy Share Image
Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you… — Brian Kernighan Copy Share Image
“Everyone knows that debugging is twice as hard as writing a program in the first place. So if you're as clever as you can… — Brian Kernighan Copy Share Image
![“Another effective [debugging] technique is to explain your code to someone else. This will often cause you to explain the bug to yourself. Sometimes it takes no more than a few sentences, followed by an embarrassed "Never mind, I see what's wrong. Sorry to bother you." This works remarkably well…” quote by Brian Kernighan](https://sms4smile.com/quotes/img-quotes/fb9/brian-kernighan-27197_bears_another-effective-debugging-technique-is_1618728.jpg)
