The dangers of clever programming

There’s often a temptation for coders to come up with the cleverest solution to a problem, one which accomplishes the greatest amount in the fewest lines of code, for example, or takes advantage of the most obscure features of the programming language. Such solutions may be intellectually very satisfying, but are often not ideal for other reasons. I really like this quote from Brian Kernighan, which I heard for the first time last week:

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.

Enjoyed this post? Why not sign up to receive Status-Q in your inbox?

Got Something To Say:

Your email address will not be published. Required fields are marked *

To create code blocks or other preformatted text, indent by four spaces:

    This will be displayed in a monospaced font. The first four 
    spaces will be stripped off, but all other whitespace
    will be preserved.
    Markdown is turned off in code blocks:
     [This is not a link](

To create not a block, but an inline code span, use backticks:

Here is some inline `code`.

For more help see


© Copyright Quentin Stafford-Fraser