Bibliography

Extreme Programming Explained, Kent Beck.

Design isn't free...When you put more design in today, you increase the overhead of the system. There is more to test, more to understand, more to explain. So every day you don't just pay interest on the money you spent, you also pay a little design tax.

Principles of Program Design, Michael A. Jackson.

There are two rules for when to optimize:

Don't do it.
(For experts only) Don't do it yet.

Programming Style: Examples and Counterexamples, Brian Kernighan and P.J. Plaugher

If you write code with care in the detailed expression, using the fundamental structures and chosing a good data representation, most of the code will be self-documenting---it can be read. Much of the need for detailed flowcharts and comments on every line will go away.

Elements of Style, William Strunk and E.B. White.

Omit needless words.