One thing we have missed in our personal virtual traveling is a convenient summary of the computer technology.  An introductory overview helps you see everything in context, so it becomes easier to control your personal computer universe.  The application's Help button or pull-down menu doesn't help you too much if you don't quite know what you're looking for, and it certainly doesn't give you the insight you need when things freeze or go inexplicably wrong.  A book on the subject can be too long, an article too loosely written or too specialized, a manual too local and specific.  A little barroom philosophy helps, too.

We don't seem to treat computers like washing machines or lawn mowers.  Sometimes, we should.  The processes taking place are just as tangible, just as tightly-linked together.  They are not mysterious, and we should be just as ready to give them a kick if something isn't working properly.  Such attitudes are not always popular with the geeks, but then a washer-dryer engineer doesn't appreciate dents in the cabinet either.  Give respect where and when respect is due.  Don't forget that much software is far less elegantly built than a Maytag; some snazzy interfaces often hide far-from-elegant code underneath.

We have to take control of this computer beast.  We should be able to impose our will and our requirements on it, rather than having to understand someone else's bizarre language structure.  There's a problem with the way many of us were introduced to computers: in the workplace.  In the office, the Information Services (sic) Department sets up a computer then tells you the rules about how you work it.  At home, never forget that you rule your own desktop, and it should serve your needs and function the way you want. But you need to know a thing or two.

A personal computer should be just that.  You should be as involved with its choice of features and its operation as with selecting your bedroom wallpaper.  Be patient. As you may remember, finding the right pattern takes time.  Unfortunately, after the initial setup done by someone else, in the rush to get going we often don't bother to figure out the simple things that are going on.  Then, if something doesn't behave as expected we don't know better than to get on the telephone.  Many of us are too impatient to understand and then to personalize the electronic environment in which we will spend hours.  We wind up tolerating things which we'd think ridiculous in our physical homes.  If it's cold, you turn up the heat.  Done.

In principle, this technology is quite simple, and built on very clear, basic blocks.  Most of the time we can set computers up as we please.  In practice, imperfect construction can lead to all sorts of strange behavior.  A dandelion growing on a bridge doesn't stop the highway, but unfortunately a single, insignificant file that gets damaged may take out a word processor with it.  The Lord giveth, and the Lord taketh away....

You can read this introduction in our suggested page order, using the Back and Next links, or skip to your subject of choice. We provide external links where they might be of interest or further help.