Richard E. Pattis

If you cannot grok the overall structure of a program while taking a shower, you are not ready to code it.

— Richard E. Pattis

Programming languages, like pizzas, come in only too sizes; too big and too small.

— Richard E. Pattis

Code should run as fast as necessary, but no faster; something important is always traded away to increase speed.

— Richard E. Pattis

When building a complex system, having crackerjack programmers (who can make any design work, even a bad one) can be a liability.…

— Richard E. Pattis

A class, in Java, is where we teach objects how to behave.

— Richard E. Pattis

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

— Richard E. Pattis

The discipline of programming is most like sorcery. Both use precise language to instruct inanimate objects to do our bidding. Small mistakes…

— Richard E. Pattis

When teaching a rapidly changing technology, perspective is more important than content.

— Richard E. Pattis

The structure of a software system provides the ecology in which code is born, matures, and dies. A well-designed habitat allows for…

— Richard E. Pattis

The three most important aspects of debugging and real estate are the same: Location, Location, and Location.

— Richard E. Pattis