In some systems, different case in files really matters. In Windows, case in
file names means nothing especially because there is no commandline
necessary to bother typing such things. Playing with Linux a bit made me
realize at times that I couldn't hit the file I wanted because some that
come in packages are in odd cases.
----- Original Message ----- From: "The Scarlet Wombat" <coconut@xxxxxxx>
Sent: Friday, March 24, 2006 7:16 PM
Subject: [bct] Re: Frustrations with how AT is taught
DB, this illustrates an issue that I have had in the past. I will not teach the use of Word, Excel or any other program without some basic instruction in files, file management and manipulation. There was no excuse for his losing 4 hours of work, the person who should have taught him is simply not paying intention, good intentions or not, he is failing the students.
I never cease to be amazed at people's ignorance of the most basic storage structures. They get an email with a picture and can click on it to see it, but move it to a folder with like pictures? Hell, they don't even know where their attachments are stored, let alone how to create a folder or move things to it. Yes, learning file basics is really critical and not providing such training really is shorting the students.
Perhaps my views on this stem from Unix and VMS, but there, you must learn file management as part and parcel of doing anything. In a way, Windows does nobody a favor in being transparant...that is, until you need to find a file.
No, your standards are not too high, you are merely seeing the results of a point and click mentality. The blind new computer users are taught, too often, by the sighted, so they learn just as you say, a few keystrokes, but have no clue of the underlying processes, which are, frankly, more important than the keystrokes.