A Quote by Brian Kernighan

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.
Perhaps we could write code to optimize code, then run that code through the code optimizer?
When debugging, novices insert corrective code; experts remove defective code.
The genetic code is not a binary code as in computers, nor an eight-level code as in some telephone systems, but a quaternary code with four symbols. The machine code of the genes is uncannily computerlike.
My basic rule is, if it could possibly come from the end user, it's not a run-time crash. But if it is my code to my code, I crash it as hard as possible—fail as early as possible.
It was a rather extraordinary conversation if you think about it -- both of us speaking in code. But not military code, not Intelligence or Resistance code -- just feminine code.
Specifically, my favorite tool in Java is hot code swapping in debug mode, meaning I can edit the code while the game is running and immediately see the results in the running game. This is super great for rapid tweaking.
Many days I don't write any code at all, and some days I spend all day writing code.
There's a definite sense this morning on the part of the Kerry voters that perhaps this is code, 'moral values,' is code for something else. It's code for taking a different position about gays in America, an exclusionary position, a code about abortion, code about imposing Christianity over other faiths.
There's a subtle reason that programmers always want to throw away the code and start over. The reason is that they think the old code is a mess. [...] The reason that they think the old code is a mess is because of a cardinal, fundamental law of programming: It's harder to read code than to write it.
Most developer tools try to shield you from actually writing code in constructing the GUI bits or the database bits. Yet when you do write code you usually get glass teletypes where high tech is keyword coloring.
Ugly programs are like ugly suspension bridges: they're much more liable to collapse than pretty ones, because the way humans (especially engineer-humans) perceive beauty is intimately related to our ability to process and understand complexity. A language that makes it hard to write elegant code makes it hard to write good code.
The word 'code' turns out to be a really important word for my book, 'The Information.' The genetic code is just one example. We talk now about coders, coding. Computer guys are coders. The stuff they write is code.
Always think about how a piece of code should be used: good interfaces are the essence of good code. You can hide all kinds of clever and dirty code behind a good interface if you really need such code.
The tax code is very inefficient. Both the personal tax code and the corporate tax code. By closing loopholes and lowering rates, you could increase the efficiency of the tax code and create more incentives for people to invest.
I do as much debugging as possible on the Mac, but I occasionally must debug problems in the PC world, which is significantly slower.
It's hard enough to find an error in your code when you're looking for it; it's even harder when you've assumed your code is error-free.
This site uses cookies to ensure you get the best experience. More info...
Got it!