One of the aspects of my job that I don’t like all that much is training. Every month or two we hire a new group of people who will work in sales and support of our product in the field. Some of these people come from nursing or tech poistions in hospitals, while others come from a sales background, and a handful don’t seem to have any relevant experience. Mix in a couple of reps from foriegn contries with varying levels of english comprehension, and you have a class that can be a challenge to teach.
I break these classes into two or three 1-2 hour sessions over a couple of days. I teach a basic unix class that starts with explaining what an operating system is, moves onto the history of Irix and Linux and why we chose them for our systems, and finally into actually using unix. Generally I touch on users, the filesystem, and the basic commands for getting around (pwd, ls, cd, mv, su, etc.) This might not sound like a lot but if you have someone who used to be a nurse and has never really used a computer before it can be a real challenge.
I then generally move onto a more advanced unix class (compared to the first at least…) This generally covers editing files, burning cds, viewing harddrive usage and freeing up space, and a bunch of stuff specific to our applications. This class is usally a lot more fun because it is pretty much all hands on and I get to see the curious interpretations of what I have taught them so far.
The most complicated class I teach is a networking and dicom class. This takes people who have never done more than search the web and in the end they are able to set up our systems to use Dicom to transfer radiological exams on a hospital network. This is usually about a 1.5 hour class. I spend the first 45 minutes explaining how a network is organized and how it works. IPs, MAC addresses, gateways, routers, the works. Well, netmasks work by “some sort of geek arithmatic” but that is good enough for them.
Then I spend about 15 minutes talking about how to enter these numbers into our systems (thank god for redhat-config-networking). Then it is time for explaining Dicom, Pacs systems, and what a Port number is. This is usally a pretty easy topic so I will spend some time talking about what can go wrong and how to trouble shoot. At this point I usually get some glossing of eyes and I know that I have gone far enough. Mix in random questions and these are good topics for classes that aren’t much more than an hour.
In the end the students don’t have a thorough understanding of any of the topics. I would be very surprised if any of them could actually set up networking without any help. That is okay though. The true goal of these classes is to teach non-technical people that using Unix may not be easy, but it certainly is nothing to be afraid of. They always buy that. Always. No one complains that copying files is hard when I am done because they understand that it is just the way it is.
People, even non-technical people, always surprise me with thier capacity for learning geeky topics.
gnubbs