mehdik / software-quotes Goto Github PK

If debugging is the process of removing software bugs, then programming must be the process of putting them in.

There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult.

 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.

When debugging, novices insert corrective code; experts remove defective code.

Computer science education cannot make anybody an expert programmer any more than studying brushes and pigment can make somebody an expert painter.

Walking on water and developing software from a specification are easy if both are frozen.

You can have the project:
    Done On Time
    Done On Budget
    Done Properly
Pick two.

Some people, when confronted with a problem, think "I know, I'll use regular expressions."
Now they have two problems.

In theory, there is no difference between theory and practice. But, in practice, there is.

A good programmer is someone who always looks both ways before crossing a one-way street.

Deleted code is debugged code.

First, solve the problem. Then, write the code.

Good code is its own best documentation. As you're about to add a comment, ask yourself, "How can I improve the code so that this comment isn't needed?" Improve the code and then document it to make it even clearer.

Without requirements or design, programming is the art of adding bugs to an empty text file.

There is not now, nor has there ever been, nor will there ever be, any programming language in which it is the least bit difficult to write bad code.

Any code of your own that you haven't looked at for six or more months might as well have been written by someone else.