The art of getting help

Vladimir Vrabec vrabec at cs.felk.cvut.cz
Thu Apr 7 17:34:46 CEST 1994


Vazeni pratele,
prikladam clanek "The art of getting help" (Phil Agre), ktery ma jiste
svuj vyznam nejen pro zacatecniky ale i pokrocile uzivatele Internetu.
Mnohem delsi praci tohoto zamereni (network), na kterou upozornuje zacatek
clanku, jsme ulozili do omicronovskeho archivu s lokatorem
"gopher://saturn.felk.cvut.cz/00/archiv/94040701-networking.txt".
                                          Prijemne cteni preje
                                                    Vladimir Vrabec
--------------------------------------------------------------------
Date: Tue, 15 Mar 1994 10:44:33 -0800
From: Phil Agre <pagre at weber.ucsd.edu>

--------------------------------------------------------------------


                T H E  N E T W O R K  O B S E R V E R

  VOLUME 1, NUMBER 2                                 FEBRUARY 1994

--------------------------------------------------------------------

  This file contains a single article from The Network Observer,
  entitled "The art of getting help".  It contains some guidelines
  about using Internet discussion groups to ask for assistance with
  research projects and the like.  For a related and much longer
  article on building professional communities on the net, send a
  message that looks like this:

    To: rre-request at weber.ucsd.edu
    Subject: archive send network

--------------------------------------------------------------------

  The art of getting help.

  In the Risks Digest 15.57, Dan Yurman <dyurman at igc.apc.org>
  complained about a worrisome new net phenomenon, "the practice by
  college students of using subject matter listservs as sources of
  first resort for information they should be looking up in their
  university library".  He tells the tale of a college course in
  which students were directed to do research for term papers on
  environmental issues using messages posted to Listserv groups.
  The result was a flood of basic questions being directed to a
  group of specialists in ecology.  His note is valuable in its
  entirety, and you can fetch it from the RRE archive by sending a
  message that looks like:

    To: rre-request at weber.ucsd.edu
    Subject: archive send courtesy

  The basic problem, in Dan's view, was that "neither the TA nor the
  students had any idea who was at the other end of the line.  All
  they saw was a computer that should be giving them answers."  That
  may well be true, but I would like to suggest that his tale raises
  an issue of much broader importance: teaching students how to get
  help -- both off the Internet and on it.  My own experience as a
  college teacher is that most students have little understanding of
  how to get help.  Many cannot seek help, for example by showing up
  for a professor's office hours, without feeling as though they are
  subordinating themselves to someone.  The reasons for this feeling
  might well be found in the workings of educational institutions.
  My own issue here is what to do about it, and how the Internet
  might (or might not) help.

  We should start by telling ourselves three obvious things: (1)
  that needing and getting help are normal parts of any project
  that isn't totally spoon-fed, (2) that getting help is a skill,
  and (3) that nobody is born with this skill.  What are the basic
  principles of getting help?  They might all sound obvious to you,
  but they're definitely not obvious to beginners -- maybe you can
  store them where beginners can find them.

   * Be able to explain your project.  If you can't explain the
  basic ideas and goals of your project in language that any given
  person can understand, then back up and figure out what you're
  trying to do.

   * Know what your question is.  Just because you feel like you
  need help, that doesn't mean you know what it is you want.  If you
  need help formulating your question, *get* help with that first.

   * Try the obvious sources first.  Never ask a person, or at least
  a person you don't know well, any questions until you've tried
  the obvious references -- encyclopedias, almanacs, card catalogs,
  phone books, and so forth.  Failing to doing so regularly causes
  great offense.

   * Make friends with a librarian.  Librarians have chosen
  to be librarians because they are dedicated to helping people
  find information.  If you're feeling uncertain about how to find
  information, go to a library and ask questions.  You'll get much
  better and more patient answers than you'll ever get on the net.
  If you don't know what to say, say this: "Hi.  I'm working on a
  project about X and I'm trying to find information about Y.  Who
  can help me figure out how to do this?"

   * Ask the right person.  Figure out whether your question is
  basic or advanced, and don't ask an expert unless it's advanced.
  It's okay to ask librarians how to find basic information.

   * Provide some context.  Unless your question is quite
  straightforwardly factual in nature, it probably won't make sense
  to anyone unless you explain something about your project first.

   * Don't get hung up on the Internet.  Think of the Internet as
  simply one part of a larger ecology of information sources and
  communication media.  Don't look for your answer on the Internet
  just because the Internet is fashionable or easy.  The Internet,
  at least as it stands today, is very good at some things and very
  bad at other things.

   * Do some homework.  Let's say you *do* wish to get information
  by sending a message to a discussion group (Listserv group,
  Usenet news group, etc) on the net.  If at all possible, subscribe
  to that group for a little while first in order to get a sense
  for it.  How heavy is the load?  How polite is the general tone
  of interaction?  Does the list maintainer have a FAQ (Frequently
  Asked Questions) file available?  (Do you figure your question
  might be frequently asked?)

   * Take some care.  Keep in mind that the people aren't obligated
  to help you; they're busy and have lives just like you.  So don't
  just dash off a brief note.  Write in complete sentences and
  check your spelling.  Avoid idioms that people in other countries
  might not understand.  Don't attempt any ironic humor; it doesn't
  travel well in e-mail.  Start out by introducing yourself in a
  sentence or two.  And wrap up with a polite formula such as "Any
  suggestions would be much appreciated."

   * Make yourself useful.  If your question might be of general
  interest, offer to assemble the answers you receive and pass them
  along to whoever else is interested.  You might even consider
  maintaining a file of useful information on the subject and
  advertising its availability to others in your situation.

   * Ask who to ask.  Consider including a statement such as, "If
  nobody knows the answer, perhaps you can tell me who else might
  know it."  Indeed, it's often a good idea to formulate your
  question this way in the first place.  That is, instead of "Can
  anybody tell me X?", try "Can anybody tell me how to find out X?"

   * Use the Reply-To: field.  Keep in mind that e-mail discussion
  groups are often destroyed by too much random chatter.  You can
  help minimize the amount of random chatter that your request
  generates by including a Reply-To: field in the header of your
  message, indicating that replies should be directed to your own
  e-mail address and not to the whole group.

   * Sign the message.  Include your name and e-mail address in the
  message, in case it isn't obvious from the header.

   * Say thank you.  Send a brief message of thanks to each person
  who replies constructively to your request.  Do not simply include
  a generic "Thank you in advance" in your request -- you risk
  making the net more impersonal.

   * Let it take time.  You won't necessarily get an answer right
  away.  You won't necessarily get an answer at all.  It might take
  a while before you learn how to use the net.  That's life.

--------------------------------------------------------------------
  Phil Agre, editor                                pagre at ucsd.edu
  Department of Communication
  University of California, San Diego           +1 (619) 534-6328
  La Jolla, California  92093-0503                   FAX 534-7315
  USA
--------------------------------------------------------------------
  The Network Observer is distributed through the Red Rock Eater
  News Service.  To subscribe to RRE, send a message to the RRE
  server, rre-request at weber.ucsd.edu, whose subject line reads
  "subscribe firstname lastname", for example "Subject: subscribe
  Jane Doe".  For more information about the Red Rock Eater, send
  a message to that same address with a subject line of "help".
  For back issues etc, use a subject line of "archive send index".
--------------------------------------------------------------------
  Copyright 1994 by the editor.  You may forward this issue of The
  Network Observer electronically to anyone for any non-commercial
  purpose.  Comments and suggestions are always appreciated.
--------------------------------------------------------------------



More information about the net mailing list