? A few months ago, CACM came close to returning to its old self l; and ran some worthwhile papers. These were papers on human i@ factors in computer system design. The section containing these ; papers had a preface, which described the experiences of a n> computer user faced by problems typical of poor human factors ? design. This month's CACM contained a letter from a fellow who o? thought that the preface displayed the attitude of a lazy user mA who didn't care to think for him/herself (don't take my word for i> it; find a copy of the issue and read it--better still, chase @ down the issue with the papers on human factors). This provoked @ me to respond; the response follows for your possible amusement 9 and consideration. (For those of you who haven't had the i6 pleasure, the incidents are taken from real live Unix > documentation and interactions with some of its devotees. The A continued adventures of the user of cars designed and documented f< like TSO, MVS, VMS, or CP/M should be worth reading also; I  commend the effort to others.)  	 Dear Sir:   < Concerning Peter Buhr's letter parodying the preface to the A special section on Human Factors in Computing Systems:  while no  A one could  dispute the claim that solving problems, whether with t< or without a computer,  requires thought on the part of the @ solver, one ought to distinguish between difficulties essential 8 to the problem and difficulties caused by bad design or 8 inadequate documentation of wha is supposedly an aid to  problem-solving. i  > To continue Buhr's analogy, let's suppose that our automotive A user suffers a true disaster: he gets what he asks for.  We join n him as he enters his car...   A When I entered the car, I was surprised to see only one light on  > the dashboard.   When I looked in the owner's manual, I found B that whenever anything went wrong, the light came on,  displaying ? a question mark.  "The  experienced  driver," the manual said, l! "will usually know what's wrong."C  6 I continued reading the manual. In the section on the < transmission, there was a list of known problems.  The list @ contained a single item: "behaves strangely on nights with full ? moons."  (Actually,Iwas rather proud of having puzzled out that < I was reading about the transmission, because it was always # referred to as "xn" in the manual.)r  @ Further  on, I read "This brash sequence of actions attempts to : get the car onto the left-hand lane of a one-way street," < followed by a mixture of Labanotation and one-letter flags.   A Later  that week, I tried a left turn. I found out that one does  A different things to turn left in each gear.   Unfortunately, the n< index only had an entry for left turns in second gear.  The @ shade-tree mechanic down the street saved my life by telling me A that that page actually had a description of how to turn left in i: all gears; they just hadn't bothered to update the index.   A Before changing the oil, I read "...an addled dipstick should be a< treated  gently.  Experience and informed courage count for  much."  A Eventually, I got to a point at which I couldn't figure out from n@ the manual what to do.  The shade-tree mechanic down the street > said, "Shoot, you don't need the manual.  You can always take 2 your car apart to find out what you want to know."A Unfortunately, the dealer could only give me the low price I got e5 because I bought the car with the insides sealed up. p  A A few  days later I found out that an error in opening the glove d( compartment disintegrates its contents.    I now own a bicycle. n  @ (Credit is due for the first paragraph of this parody extension ? to an unknown person who entered the essentials of it into the r fortune data base at Berkeley.)i   Yours truly, James Jonese  