The discipline of programming is most like sorcery. Both use precise language to instruct inanimate objects to do our bidding. Small mistakes in programs or spells can lead to completely unforseen behavior: e.g., see the story, "The Sorcerer's Apprentice". Neither… — Richard E. Pattis Copy Share Image
If you cannot grok the overall structure of a program while taking a shower, you are not ready to code it. — Richard E. Pattis Copy Share Image
Programming languages, like pizzas, come in only too sizes; too big and too small. — Richard E. Pattis Copy Share Image
Code should run as fast as necessary, but no faster; something important is always traded away to increase speed. — Richard E. Pattis Copy Share Image
When building a complex system, having crackerjack programmers (who can make any design work, even a bad one) can be a liability. The result,… — Richard E. Pattis Copy Share Image
When debugging, novices insert corrective code; experts remove defective code. — Richard E. Pattis Copy Share Image
The discipline of programming is most like sorcery. Both use precise language to instruct inanimate objects to do our bidding. Small mistakes in programs… — Richard E. Pattis Copy Share Image
When teaching a rapidly changing technology, perspective is more important than content. — Richard E. Pattis Copy Share Image
The structure of a software system provides the ecology in which code is born, matures, and dies. A well-designed habitat allows for the successful… — Richard E. Pattis Copy Share Image
The three most important aspects of debugging and real estate are the same: Location, Location, and Location. — Richard E. Pattis Copy Share Image
