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

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

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 evolution of all the components needed in a software system.

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

When building a complex system, having crackerjack programmers (who can make any design work, even a bad one) can be a liability. The result, after lots of effort, is a working system that cannot be easily maintained or upgraded. Good -but not great- programmers would fail early, causing a realization that the system must be redesigned, and then reimplemented. The extra cost is paid once, early in the system's cycle (when it is cheap), instead of repeatedly paid late in the system's cycle (when it is more expensive).

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

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