🚀 go-pugleaf

------------------ Message forwarded by NETTRAIN moderator ------------------

Date: Mon, 22 Feb 1993 11:32:44 -0800 (PST)
From: Lee Jaffe <jaffe@scilibx.ucsc.edu>

Having just taught a day-long Internet introduction, I have a number of
observations.  Essentially, I'm in agreement with Anne Lipow's points
though I have some quibbles.  I think introductions should be just as she
describes, an awareness building sessions.  And therefore should be a
combination of lecture, demonstration and a good handout, providing a
basis for independent follow-up for those who take the hook.  I also agree
that targetting skill levels doesn't work; that people misidentify their
level and are apt to be disappointed that the class was too basic or too
advanced for their needs.

On the other hand, I think that actual hands-on training should be broken
up into very specific areas.  This, in part, answers the problem of people
finding the session that meets their needs.  If you advertise the session
as an introduction to Internet electronic mail, those who want to learn
FTP won't be sitting for an hour or two waiting for that portion.
Equally, the person that just wants to get started on email, isn't
consequently overwhelmed by the sections that follow the one they came
for.  I also want to echo earlier suggestions that you be very specific in
any announcements about the nature of the session.  Not only should you
say what the subject and format of the class will be, but also the
platform or systems that will be used.  If you are teaching email, say
that BSD Mail or Pine or Eudora will be used.  For Telnet and FTP also let
folks know that you will be demonstrating/teaching these on a Unix or
another platform.  And I would give a total of 3 hours, including breaks,
for each part.

-- Lee Jaffe, UC Santa Cruz


> Date: Fri, 19 Feb 93 09:42:12 PST
> From: alipow@library.Berkeley.EDU (Anne Lipow)
> [EXTRACTED]
> 1.  Forget about breaking the subject down into several modules that are
> offered on different days...
>
> Two types of session max: awareness
> building and hands-on training.
>
> 2.  It doesn't work too well trying to reach several different skill levels
> in different sessions.
>
> 3.  Handouts--attractively done--are critical to take care of the beginner
> and advanced.

> 1.  Introductory "awareness building" session: 1-1/2 hrs to cover the 3 basic
> services is probably too short.  Two hrs. minimum, with a 10-15 min. break
> if you include NO discussion.  Three hours, with a break, is ideal.
>
> 2.  Hands-on training:  3 hrs.  Prerequisite: must have an account.  Content:
>  30-minute overview; 1 hr. on mail/listservs; 1 hr. on ftp.  Rest taken up
> with discussion and break.  For every 7-10 attendees, you should have a
> lab assistant helping individuals catch up.
>
> --Anne Lipow