Path: utzoo!utgpu!attcan!uunet!husc6!rutgers!ucsd!sdcsvax!beowulf!pluto
From: pluto@beowulf.ucsd.edu (Mark E. P. Plutowski)
Newsgroups: comp.cog-eng
Subject: Re: Technological overcomplexity in 1523
Summary: plows and such.
Keywords: cognitive engineering, design, comnplexity, history of technology
Message-ID: <5193@sdcsvax.UCSD.EDU>
Date: 3 Aug 88 20:14:11 GMT
References: <585@sdics.ucsd.EDU> <17596@glacier.STANFORD.EDU> <587@sdics.ucsd.EDU> <1383@hp-sdd.HP.COM> <693@tetra.NOSC.MIL>
Sender: nobody@sdcsvax.UCSD.EDU
Reply-To: pluto@beowulf.UUCP (Mark E. P. Plutowski)
Distribution: all
Organization: EE/CS Dept. U.C. San Diego
Lines: 39

In article <693@tetra.NOSC.MIL> embick@tetra.nosc.mil.UUCP (Edward M. Embick) writes:
>>>John Nagle provides a much more detailed analysis of why the plow is
>>>so complex a device.  Plus an anology with modern computerware.  But
>>>that now lets us discuss how one should design so as to deal with this
>>>apparent complexity.
>>>
>>I think a better variation on the above, is to provide the user with
>>a set of basis operations from which a larger set can be derived.
>>		... etc. ...

>The ideal approach is to have an underlying design that adjusts the level 
>of prompts, and the macro capabilities of the user's commands, to the
>perceived level of user competence. ... 
>...  The system would, of course, back off at increasing the
>options if user confusion or excessive errors were detected.
>
>Our farmer would have a plough that would automatically adjust blade angle,
>ox, horse or tractor, etc., or the farmer could lock the blade and hook
>onto a cow.

Having been a farmer, i can say that this is something one might have
seen back when plows were relatively new technology.  Look at the 
antiques, they sometimes have all kinds of neat features, not found
common on current models.  Current models are well-suited to the land
upon which they are to be used.  So you buy the right plow for the land.
(same thing is done for automobiles, they are tuned for the area
in which they are to be sold).  Result: cheaper plow, less complex,
easier to use, nothing that isn't needed is needed to be purchased.  
If something is needed at a later date, it *can* be added, 
by adding modules (colters, shanks,etc.).

----------------------------------------------------------------------
Mark Plutowski
Department of Computer Science, C-024
University of California, San Diego
La Jolla, California 92093
INTERNET: pluto%cs@ucsd.edu	pluto@beowulf.ucsd.edu	
BITNET:	  pluto@ucsd.bitnet
UNIX:	  {...}!sdcsvax!pluto