Slashdot Mirror
What Should One Know to be Truly Computer Literate?
rbannon asks: "Computer literacy is becoming an increasingly used term in education, and more and more schools are being asked to set computer literacy goals for their students. Unfortunately for too many, it means being able to use Microsoft products, and that's all. However, I see it much differently, and I cannot help but think that computer literacy is all about using computers to be able to communicate more effectively. With that in mind does anyone have any recommendations for computer literacy goals, and how to measure them?"
You can't measure computer literacy without a context because "computer" is such a vague term these days and "computers" are used by many people for many different things.
FOr the average office worker it's knowing how to use MS Office. For the Hardware Engineer it means something completely different and for the software developer it's different again.
You can only be "truly computer literate" in the context of a particular field.
It's like asking for a "skilled driver" - skilled to what level? Skilled enough to navigate through suburban traffic or to compete in a Gran Prix?
"Who says nothing is impossible? Some people do it every day!" - Alfred E. Neuman
The basic rule of thumb I would use is that if you've taught them with one operating system, and they don't have any difficulty accomplishing the same tasks with another operating system of the same basic design, then they've learnt the basic concepts well enough as opposed to learning by rote what to click.
Bogtha Bogtha Bogtha
It shouldn't be about being able to use certain products or being able to do a specific task, the real goal should be teaching the kids to find out how to do things for themselves.
Give a man a fish, feed him for a day. Teach a man to fish, feed him for a lifetime. Teach a man to learn things for himself, and he'll be a hell of a lot more than a fisherman.
A literate person is one who can learn anything given time and opportunity, not someone who's read everything.
A computer literate person should be one who grasps a foundation of knowledge that prevents dead ends and allows learning whatever the current task requires.
The key concept would have to be that a computer is a playback device for software, that whoever controls the software owns the computer (yes, owns. Which gives you more control, being handed car keys, or being handed a root password?), and that some software is much better than other software. Teach that and you've cured all the people who think Internet Explorer is "the internet".
If you want to teach people to use a computer to commmunicate better, then teach them to communicate better. Outlining is a skill that is even more useful for web pages than it was for text. Good composition skills are indispensable. Old-fashioned "rhetoric" classes have a lot to offer about conveying and supporting ideas. Where text is considered obsolete, teach the "grammar" and "vocabulary" that filmmakers have worked out for multimedia works.
Know what is acomputer, how it works on a basic level, CPU, Memory, Harddrive, Video/Monitor. A computer literate person should know how theese work together under the command of an OS, have a basic idea about what an operating system is and what is the different betwean an OS and an Application
IMHO if one knows these will be able to use basic applications (including MS Office if that is what he/she desires) and call him/herself computer literate.
Understanding that a car has engine, wheel, steering wheel, transmission is necessary to drive a car. Knowing the same basic things about a computer is the same.
Than if they are programmers, network admins, webmasters - they are not computer literate's any more. They are specialized pretty much like car mechanics...
An executive, administrative person etc. is computer literate if he/she knows this - otherwise they are trained monkeys^H^H^H^H^H^H^H users, and are afraid to do anything that wasn't in the training - in consequence they will be unable to use other programs that they are trained in.
But at the same time i can teach a monkey to fit the different shaped components together and put a disc in the drive. Seriously, i know people who've built computers that have no idea what the difference between PCI/AGP/PCI-X is and they'll blindly open attachments and download programs that offer great "weather forecasts". putting tab A into slot b is no big difference from double clicking an icon on the desktop. Explain it to them once or and most people can do it over and over without having any understanding. And installing an OS like XP does nothing to educate them. Once again its a simple matter of put disc in drive, press power, select yes a lot (Put in key, that part gets tricky) and then they have a full working machine. Unfortunately with the ease of new systems its hard to find a reason to learn the basics, like when i started with with my old Apple IIe and then later DOS machines. but then again most people dont need to know this anymore, as everything is so automated nowadays. Basic skills such as what is a program, what is an OS, etc would be the most important things i would teach a complete newbie. That and common file extensions and turn off "hide file extensions" seriously that has to be one of the biggest security issues in XP in my mind. paris hilton nude.jpg.exe is probably one of the more sucessful viruses out there
drunk chemists
No one agrees with me on this, but I think that you have to know a computer language to understand computers. It can even be something like LOGO, for kids. I'm not suggesting that someone has to know a set of GUI widgets for a modern desktop or anything.
If you know a language, you know what an algorithm is, even if you don't know the word. And if you know what an algorithm is, you pretty much know what a computer is.
I'm a giant fan of that MIT vision -- LOGO for kids, extensible and scriptable apps for adults, cheap laptops for people in parts of the world where money is scarce, open information on the web, etc.
I don't have kids, though, and I've never convinced anyone that their kids would be better of learning LOGO than powerpoint. Everyone says the same thing -- you don't have to be an engineer to drive a car.
I was lucky -- I got to learn about computers with a KIM-1 single board machine, and timesharing on a PDP-10, reading books about games written by hippies. If I wanted to play a game, I'd usually have to port it from one dialect of BASIC to another. It wasn't really hard, and it's not really fair to call them ports. But you had to understand the code at least a little bit.
I think it would be a lot harder to learn from iTunes.
Computer literacy is one of those things that covers a lot of ground. In my mind, this includes a basic familarity with hardware. A savvy individual should be able to plug in a new network card, or a new hard drive. These are not advanced hardware tasks. I also think a certain amount of hardware troubleshooting is needed; a user should be able to tell if they have a dead network conntection, or a dead monitor, or a dead computer (or a dead mouse...yes, I've talked to people who can't tell. One lady even triumphantly told me that not only had she replaced the mouse (four times, according to her), she had also replaced the mouse pad. Her problem was a mouse problem, and it was fixed by replacing the mouse).
As far as software, I think computer literacy means needing to be able to figure out a piece of out-of-the-box software. Not the ability to use word or office, or whatever, but the ability to sit down in front of an unfamiliar piece of software, and fiddle with it in an intelligent way. The ability to look up a manual and read it.
It's not about being a power user. Not everyone is a power user. Most people aren't, really. It's really, in my mind, just about not being helpless when confronted with something new.
ad logicam Claiming a proposition is false because it was presented as the conclusion of a fallacious argument.
The biggest problem with learning how to use computers I've seen from neophytes is the fear of trying stuff. Everything I know about computers comes from wanting to find out how stuff works. I tinker and mess around and do stupid things and eventually figure out what things are and how they work.
Too many people are afraid they'll break the computer and resort to memorizing what they are shown. Since they only do the one thing they are trained to they are unable to grasp the underlying components and what it all means.
To be literate you have to tinker. Try stuff. Break things, get someone to fix them. Then try some different stuff.
Whenever I have a question like this, I try to devise a similar question from a non-computer perspective (a different context) to help me wrap my brain around the idea. This also happens to work especially well when trying to explain computer issues to those who are not computer literate.
For example, "What does vehicle literate mean?" A car, like a computer, is a single complex machine that the average person above a certain age is expected to know how to operate. So how does one become "car literate"? Because you know how to drive one vehicle does not mean you can operate a boat or airplane or the space shuttle. So "computer literate" probably does not mean that you can operate any computer, just the most common variety (e.g. Windows and Office). Even then, you might know how to drive an automatic and not a standard (Windows vs Linux).
Analogy is a great tool to not only improve others understanding of a given concept but also your own.
Just for fun consider this: Computer support technicians and doctors are similar in many ways. They are both supposed to be highly paid, highly trained, highly skilled, and highly knowledgeable about an extremely complex machine that they did not design or create and of which cannot possibly know everything about. Often, they rely on their limited experience to make a best guess about the root cause of the machine's particular problem and then follow up with lots of testing to see if they are correct or not. As you probably know, some computer support people, trained and certified or not, seem to have an innate gift for solving computer problems while others should never be allowed to touch a computer. Makes you think about your doctor, eh?
Ouch! The truth hurts!
That's like saying you should be able to assemble a car before you can drive. Or put a stove together before you can cook. The fact that you even think this is another indication that many of the people who work in IT (or have serious interest in it) don't understand what the end user really needs. A normal, everyday user should be able to get real work done easily without having to understand all of the jargon that you and I understand. It's absurd to expect him to do so.
David
How do you go to a website? Do you know what the #1 search on Yahoo is? It's "Google". My parent's computers are set up with Google as the home page. Do you know how they get just about anywhere? Searching google. Want to go to "favoritestore.com"? Well you type "favoritestore.com" in the Google search field and hit Search then click on the right one that comes up. They also use bookmarks. That one took a LONG TIME to break. I can not tell you how many people I've seen with that one.
Also, what is a home page in your web browser? That's the company that sells you your internet service! We subscribe to Google. We never get a bill from them. We do get bills from Comcast for Internet. But that little logical inconsistency doesn't seem to occur to them. I think I've got this one through to my parents too, but I'm not sure. I know it is (at least in part) related to AOL. The fact that you can change this to whatever you want is important and should be mentioned.
The last one for now is a personal pet-peeve of mine. I run into this in the otherwise very smart and computer savvy people in my high level CS classes.
This - / - is a FOREWORD-slash
This - \ - is a BACK-slash
One leans forward, the other leans backward. The terms are NOT INTERCHANGEABLE. The mean DIFFERENT things.
Of course this wouldn't be a problem is MS stuck with / as a path separator for DOS just like UNIX used, but that's another argument.
Comment forecast: Bits of genius surrounded by a sea of mediocrity.
Back up a bit. I don't think putting together a computer is either strictly necessary or strictly helpful. Once the person has put it together, and installed the OS, they've got this screen staring at them, asking them what they want to do. And they'll have no idea.
I can suggest several branches of computer literacy:
1): the ability to interact with common GUIs. Know what a mouse is, be able to click it and make things happen. As a bonus, add right-click (or whatever the hell you Mac people do). Learn to read dialog boxes and respond to them.
2): Learn to open common applications, and interact with common applications such as a web browser and a word processor. Know what a file is and how to save one. Know what the directory structure is and at least one way to navigate it.
3): Absolute basic hardware! Be able to take your computer apart, move it to a different room, stick all the things in the back in, and have it work as it did before. Knowing the various jacks by sight might get bonus points, but isn't strictly necessary.
4): Regular maintenance. Know what a virus is, and why you have to keep your virus definitions up to date. Know what a patch is, and why you're supposed to install one.
5): More theory. Learn basic technical concepts, like what an operating system is, what an application is, the difference between memory, hard drive, processor, networking.
6): Internet basics. Understand that when your computer loads up a web page, it's actually talking to another computer. Understand the concept of "bandwidth" (using a hose analogy if needed). Understand the difference between the Web and the Internet. Know that computers identify each other by numbers known as "addresses", and that the domain names are simply a way of mapping from memorable names to those numbers.
7): Security. Know what a firewall is and what it does. Understand why you don't run attachments sent by random people. Have some idea of what constitutes a good password.
I think if you know all this, it would be a rather stingy society that wouldn't call you "computer literate". Your approach would probably go a long way towards getting some of the concepts down, but it's only a starting point.
You want the truthiness? You can't handle the truthiness!
>Last, and most important UNDERSTAND THE FILESYSTEM. I've gotten my parents quite good at day-to-day use of the computer. It has taken YEARS.
The fact that noones parents understand the filesystem is an indicator of exactly one thing
THE FILE/FOLDER METAPHOR IS BROKEN
Yes, the whole idea of 'files' is only a metaphor. Even in Unix. A very useful metaphor, sure. But it's not necessary or helpful anymore for the average user.
It's great that files exist, and in *nix-likes are the basis for everything, sure. But the user doesn't need to see these pesky files anymore, they are just confusing him. He should know be one level of abstraction up - working with something we could call a 'document', for want of a better term. He doesn't need to know if his webpage consists of multiple files. It's just a document. If he has the same piece of content in multiple formats, he doesn't need to know that either. It's just a document. He should be able to preserve multiple versions restore points of his document, w/o worrying about having different files with different names. It's just a document.
Fact: most techies understand treelike structures well, and did even before hierarchical filesystems became common currency. For obvious reasons.
Fact: most people's mom encountered her first treelike structure the first day she typed a document in Word, and wanted to save it.
MS realized as far back as W95 that the filesystem hierarchy wasn't particularly intuitive to the average member of the W95 target market. Rather than do something revolutionary and innovative which would have made everyone's lives easier the last 10 years, they mucked around with it a little bit, made some cosmetic changes, tried to please both the new people and the experienced people, and ended up fixing not much, and breaking things which were at least consistent in DOS.
My dad figured out that since he had 2 versions of the folder 'My Documents', one contained in My Computer, and one not (on the desktop), one was storing his files locally, and the other was storing them somewhere else, not on his computer. He even renamed the folder in the C: drive "My documents here" so he could tell them apart. (on winME btw)
This isn't an obligatory MS-bash. IMHO, it's a lot more shocking that no linux distro/desktop manager, has tried to sort this out. They are the ones that have the opportunity to make fairly sweeping changes. Linux users would catch on fast, appreciate an elegant solution, and still be competent to see 'behind the scenes' to the actual filesystem if desired. The same goes for Apple to some extent, and for some slightly different reasons. MS themselves have their hands much more tied as to what they could change, now that everyone has 10 yrs experience of Windows doing it the dumb way.
In a previous slashdot story about similar stuff, someone said that their mom used a single word document to type everything, and printed out the relevant pages each time.
Older people are not stupid, but they are being made to feel stupid by stupid designers, programmers and documenters, and as technology becomes more important this is more and more damaging to their lives.
* to all the older slashdot users, computer able seniors, and slashdotters with techie parents, sorry to make generalizations but they are broadly true..
my password really is 'stinkypants'
A person needs to know enough to RTFM.
The fact that noones parents understand the filesystem is an indicator of exactly one thing
THE FILE/FOLDER METAPHOR IS BROKEN
Yes, the whole idea of 'files' is only a metaphor. Even in Unix. A very useful metaphor, sure. But it's not necessary or helpful anymore for the average user.
I'm gonna have to disagree with you on this one. People have been using hierarchical paper files for hundreds if not thousands of years. It's a basic organizational system, and is a minimum for working sanely with large numbers of files. The confusing thing is that the user's files are saved in the same filesystem as all the system and application stuff, so the hierarchy itself is overwhelming. I can understand the need to separate those.
Older people are not stupid, but they are being made to feel stupid by stupid designers, programmers and documenters, and as technology becomes more important this is more and more damaging to their lives.
This is a common argument, but I think you underestimate how hard it is to make things usable. The trick is to make things as simple as you can but still have the necessary features. I think Apple has been hitting a sweet spot here for a while with iLife.
The problem is essentially that many many people do not have the patience to figure out a complex system. They approach a program with the desire to do one thing, and the only way they could be satisfied is if there is a big button on the screen that says "Do the Thing". However, that same user may potentially want to do 100 different things at different times, and they certainly won't be satisfied by a screen filled with one hundred buttons. Hence the purpose of menus, wizards, hierarchies, preferences and all the other complications us geeks know and love.
There are a large number of people who do not want to think about how to do something or where one might logically find some aspect of a computer program. These people get anxious just looking at a dialog box. They do not enjoy figuring things out.
I'm sorry, but you are not going to design an interface that meets the lowest common denominator and is still useful. It just ain't gonna happen. To get to that point what we need is full-blown artificial intelligence. In other words, a replacement for the techie that they call on the phone to tell them how to do something. It's so easy to blame the designer, and I agree a lot of interfaces are horrendous, but the reality is that there is a certain amount of irreducible complexity inherent any moderately useful general purpose computer system. People who want to do one thing and have no patience for learning any context should be given appliances that do the one thing they want. That's the only way to make things usable for them.
I'd add in a few basic skills to consider someone computer literate.
Program agnosticism: They should know roughly how chat programs work. This doesn't mean AIM, this means that they know enough that they can walk up to any chat system and make it do useful things. Same thing for e-mail clients. Same thing for Browsers. You should be able to give them a laptop loaded up with Windows or Knoppix or SkyOS, and they should be able to quickly muddle their way over to myspace.com.
Hardware knowledge: This is your power supply. When it breaks, things tend to smoke. This is a hard drive. When it breaks, it makes a "click click click Screeeeech!" noise. This is your graphics card. Also known as the hole you'll be pouring your money into for the rest of your life. I'm not saying everyone should have memorised the jumper settings on their motherboard. But they shouldn't be afraid to open the thing up and look or make changes.
Some Scripting: I don't care what scripting language. I don't care if you're talking Perl, Word macros, applescript, AutoHotKey, a command line script, an e-mail filter, or Java. If they can write things in a scripting language, even a completely visual handholding one, they're good. You don't need to fully program or compile. You don't even need to be that great at it. You just need to be able to think about the problem in terms of "how do I tell this computer how to do something."
The ______ Agenda
Level zero is realizing that
The Computer is not the big box on the table
The Harddisk is not the big box under the table
The Color of the box does not matter
It's not "how many RAM's" but "how much RAM"
Level one is realizing that
Text editing is not Word
Spreadsheet is not Excel
Presentation is not Powerpoint
Communication is not Outlook
News is not Explorer
The Internet is not WWW
i.e. realizing what you don't need a specific program to fullfill a specific task.
What is magic? Words and symbols of power that shape the world according to the will of the magician. The magician speaks the right magic words, and draws the right sigils, and obtains the desired effect.
Meanwhile, the INT 8 half-orc barbarian doesn't have the faintest idea what all the runes carved on his battleaxe actually do. He doesn't care. He knows the end result is a +1 to hit and that suits him just fine. Neither is the ranger concerned about exactly how these enchanted bracers improve his aim with a longbow; they just do. Only the wizard needs to worry about the details.
And what is programming? Words and symbols of power that shape the computer according to the will of the programmer. Type the right instructions, give the right command arguments, and obtain the desired effect.
Ever created an infinite loop? Had a recursive process go berserk on you? Made a small mistake while invoking rm -rf? Yeah. Pure 'Sorcerer's Apprentice'.
We are the nearest thing to magicians that has ever existed in reality. Our spells work and are truly powerful, our mistakes cause incomprehensible chaos, and when one of us turns bad then sometimes the whole world can suffer the consequences. No wonder the muggles treat our creations like they're the mysterious products of a magical power beyond their understanding: that's what they are.
Real Daleks don't climb stairs - they level the building.