Linked by Kevin Russo on Tue 7th Dec 2004 06:19 UTC
Permalink for comment
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
More News »
Sponsored Links



Sorry, you're working on a false assumption. You assume that if the user doesn't know that to do X they need to edit X, Y and Z that means they don't know what X, Y and Z are. This simply isn't true. To take a random example, I had no idea how to set up bluetooth under Linux when I first got a bluetooth usb adapter. I needed to install rfcomm and a few other utilities and edit some configuration files under /etc. If someone simply says to me 'install rfcomm, edit X Y and Z config files' that is enough to get the job done (and in fact the instructions I eventually used were very much in that style). I don't *need* to be told 'go to a console, type 'urpmi rfcomm', then type cd /etc and then gedit blahblah.conf'...
As I said, IMO it's reasonable to start off working as if the user you are helping is of this type (unless the question is so basic that it's obvious the user must be at a lower level). If it transpires that they can't understand this high level form of assistance, use a lower level one.