Computer Stupidities
Stephen R. van den Berg writes "Yet another BOFH [?] -relief site:
stories about Computer
Stupidities compiled by
RinkWorks.
"What do you mean, other tape?
When it said second volume, I just hit
enter again.". "
← Back to Stories (view on slashdot.org)
However, after spending a good afternoon reading these stories, I note that many of them involve a user who assumes that he knows more than the tech support person or a tech support person who won't consider the obvious.
When a user calls up, claims to be an "Apple Tech," and then proceeds to ask how to do something simple the techie tells him to do, he rightfully should be mocked. When the user refuses to take the advice of a knowledgeable tech and then threatens some sort of recourse because "the tech doesn't know anything," they rightfully should be mocked.
The problem with many computer users is that they get proficient with using MS Word, figure out how to drag and drop, and install a program or two while surfing the web using AOL and they decide that they're an instant A+ certified MSCE know-it-all. I've got friends like this. One of my (least) favorites thinks he knows all about designing web pages. He's decent at Photoshop and knows a bit about WordPerfect. One day, he applied for a job where I work, and told the folks that he had a "vast knowledge of computers." The next day he called me wanting to know how to put in a CD-ROM drive.
I'm often reminded of the "General Motors Tech Support" joke that was circulating about two years ago, where a user calls up tech support because his car won't start. When the support guy tries to get the user to check things out, he is met with replies like: "What's a steering wheel? What's a dashboard? Fuel Gauge? What's That?" Finally, the exasperated user exclaims "I'm not a technical person! I just want to go places with my car!"
Although it seems ludicrous that we would allow someone with such limited knowledge to pilot an automobile, we do the same thing with computers every day. I'm not saying that people who don't know computers shouldn't be allowed to use them -- I'm saying that most people realize that a certain amount of knowledge is necessary to drive a car on our highways. Computers users need to realize that despite the fact that they might want to do something useful with their new toy, they are going to have to take some time to master some concepts.
Incidentally, I'll go the other way in terms of blaming why computers are so hard to use - it's the level abstraction set up between the user and whats really going on.
/wants/ to look at it and know whats going on, s/he can. And yet, people who don't know anything about engines just don't touch theirs, and refer to experts when it comes time to fix it. But at least they can see it, and chose to learn about it and fiddle with it if they want to. If a proper interface was set up bewteen the low-level and the high-level in an OS, the user should recognize properly what not to touch, or conversly, what to touch when they want to fiddle and learn. Barring this low level from the user (such as in most Windows 9X componants' interfaces) makes them live on another plane of reality from whats really going on, and leaves them clueless when its time to fix things of describe whats going on to tech support.
For example, I'll propose that the newbie Windows 95 user hasn't a clue what a "Shortcut" is with respect to the idea that its an actual file on the disk with a special file type. They're just told it's a "Shortcut" and how to work it. These types of abstractions only serve to convuse new users as when it comes to problems, they havn't the faintest idea what they're actually supposed to be fixing, nevermind how to. How are they supposed to know when a problem is because of the shortcut, or the actual file it points to? Similar abstractions (wizards, "dumbed down explainations") may serve to help the uninitiated get off the ground faster, but makes it all the more difficult for the user to make an emergency landing when it comes time.
Cars are complex things. Why do auto makers not lock the engine from the driver? Because if the driver
"Old man yells at systemd"