Fixes from Albert Reiner

There's more to good interface design than that. Allow me to introduce

a design element which I call the ``interface component.'' The purpose

an interface component is to implement, and

of an interface component is to implement, and

\emph{hide information about},%

\index{I!Information-hiding}

the data interface between two or more other components

and objects in the application.  The choosing of names turns out to be

an important part of the design process.

Newcomers tend to overlook the important of names.  ``After all,''

Newcomers tend to overlook the importance of names.  ``After all,''

they think, ``the computer doesn't care what names I choose.''

But good names are essential for readability.  Moreover, the mental

and data to reduce redundancy.

We can also apply limited redundancy during compilation, by letting

\Forth{} do some of out dirty work.

\Forth{} do some of our dirty work.

\begin{tip}

For maximum maintainability, limit redundancy even at compile time.

(Streets run east and west; avenues run north and south.)

%% I changed "We want" to "we want"

Now, to define the left margin, we might compute it mentally, We want

Now, to define the left margin, we might compute it manually. We want

to center all these boxes on a screen 80 columns wide. To center

something, we subtract its width from 80 and divide by two to

determine the left margin. To figure the total width of all the boxes,

\begin{tfquot}

This morning I realized I've been mixing the descriptions of the chips

with the placement of the chips on the board. This perfectly

with the placement of the chips on the board. This is perfectly

convenient for my purposes at the moment, but when I come up with

another board that I want to use the same chips for, I have arranged

things very badly.