Code Quality Quotes

Good visual layout shows the logical structure of a program.

An API that isn't comprehensible isn't usable.

Time pressure gradually corrupts an engineer's standard of quality and perfection. It has a detrimental effect on people as well as products

At first I hoped that such a technically unsound project would collapse but I soon realized it was doomed to success. Almost anything in software can be implemented, sold, and even used given enough determination. There is nothing a mere scientist can say that will stand against the flood of a hundred million dollars. But there is one quality that cannot be purchased in this way - and that is reliability. The price of reliability is the pursuit of the utmost simplicity. It is a price which the very rich find most hard to pay.

Programs should be written and polished until they acquire publication quality.

Don't document bad code - rewrite it.

Testing by itself does not improve software quality. Test results are an indicator of quality, but in and of themselves, they don't improve it. Trying to improve software quality by increasing the amount of testing is like trying to lose weight by weighing yourself more often. What you eat before you step onto the scale determines how much you will weigh, and the software development techniques you use determine how many errors testing will find. If you want to lose weight, don't buy a new scale; change your diet. If you want to improve your software, don't test more; develop better.

The simple fact is that code quality tends to improve as you move between platforms... non-obvious bugs on Windows become VERY obvious in the Linux port and vice versa, and thus get fixed. So even the Windows gamers will win in all of this.

Most software today is very much like an Egyptian pyramid with millions of bricks piled on top of each other, with no structural integrity, but just done by brute force and thousands of slaves.

Are you quite sure that all those bells and whistles, all those wonderful facilities of your so called powerful programming languages, belong to the solution set rather than the problem set?

Releasing Linux versions has always been a matter of higher code quality, good software architecture, and technical interest for the platform.

Measuring programming progress by lines of code is like measuring aircraft building progress by weight.