Are You Making Your Family Technologically Illiterate?
-
-
ehhhhhhhh
If my hypothetical wife was better at first aid than I am, and she takes care of all wounds - does that make me first-aid illiterate?
Sharing the burden of housework is ok. There is a point where it's detrimental to over-help but isn't that the same with everything else?
Edited because english is my first language and the post didn't reflect that so I made it gooder.
-
I think what they were getting at is that most people enhance and grow the technical literacy by doing and troubleshooting. If you stop keeping up with changes and never troubleshoot, you will atrophy. Imagine if you stopped reading at a first grade level and always had someone read to you your entire life. You'd get worse and worse at reading over the years. Now imagine that the language evolved at a noticeable pace with new letter shapes and word forms every few years. Imagine how illiterate you would be after a decade of not seeing any new words and not having practiced what you knew before.
-
I think it's the other way round. In households where one person is tech savvy there is a tendency to tinker, fiddle, experiment and ultimately break things. The non-IT person then has to either wait for it to be fixed, or give up waiting and fix it his/herself.
-
@Carnival-Boy said:
I think it's the other way round. In households where one person is tech savvy there is a tendency to tinker, fiddle, experiment and ultimately break things. The non-IT person then has to either wait for it to be fixed, or give up waiting and fix it his/herself.
Or in the case of my house (both growing up and after getting married) -- whoever doesn't do the technical work starts trying to fix it themselves, and soon they become proficient at doing at least some level of tech work -- even if they only do it for themselves.
-
Wow.. you two live in a wonderful world! I'm sure if I had kids, the kids surely would try to fix their own problems, but my wife doesn't care about how it works, only that it does work... and will instead of trying to fix it, choose to do something else until I'm available to repair/resolve the problem with whatever is wrong.
I completely agree with where this article (and Scott) are going with this, and I see the trend every day in my office.
When I called upon to resolve problems, I try to educate the individual who is having the problem on what was wrong and how they can fix it in the future. This is especially true of common tasks, rebooting a computer, putting paper in a printer, etc. While I do show them the other much less common things, how to set a signature in Outlook, but also follow up with, I'll understand if you don't recall how to do this in the future since this happens so infrequently you probably won't remember."
What frustrates me though, is that even on the common tasks, how to unjam a label Dymo Labeler, how to change their default printer (something most have to do daily because they work in two plus environments) is that they just don't care to learn it, even after asking 10 times and learning it would get them resolved in half the time or better. -
@Dashrender said:
Wow.. you two live in a wonderful world! (snip)
I did have a relatively good childhood, lol. No major catastrophes struck, and I learned a lot from my old man. 8-) My kid is only 4, so he's not quite ready to start fixing his own problems yet. But I still let him try and teach him to ask for help when he needs it!
I completely agree with where this article (and Scott) are going with this, and I see the trend every day in my office.
(snip)... is that they just don't care to learn it, even after asking 10 times and learning it would get them resolved in half the time or better.By and large, especially in a corporate setting, i will agree with this as well. I hilighted the real problem... Most of the time they just don't really care to learn anything outside of their job.
-
What's sad is that they don't really need to care - instead they just need to realize they can make their own lives better by learning a few of the things we try to teach them so they aren't just sitting around waiting for something to be fixed. It's not like we are a bunch of union workers and are going to fine them for taking our work away.
-
@Dashrender I'd upvote that comment 10,000 if I could.
-
@Dashrender said:
I'm sure if I had kids, the kids surely would try to fix their own problems
Yeah, I sometimes get support calls at work from my 10 year old: "Dad, I can't get Minecraft to work". He's already better than half of my users in that he always tries turning it off and on again to see if that fixes it before bothering me with a call
-
@Dashrender said:
we try to teach them so they aren't just sitting around waiting for something to be fixed.
Sadly, I think a lot of people like sitting around waiting for something to be fixed. For them, it beats working.
-
My brothers (all adults) have figured out if they call me my first 2 questions are going to be did you turn it off and then back on again and did you look it up on google before calling me. Now one of them never calls me anymore.
We homeschooled so I never really just answered a question for @Mike-Ralston he always had to go find the answer himself, if he still needed help after that then I would help but never on the first go around.
-
I didn't realize @Mike-Ralston was your son.
-
@Carnival-Boy said:
I think it's the other way round. In households where one person is tech savvy there is a tendency to tinker, fiddle, experiment and ultimately break things. The non-IT person then has to either wait for it to be fixed, or give up waiting and fix it his/herself.
How often do you think, though, that an IT person will break something beyond the point of them being able to fix it and then the non-IT person can just "figure it out?" Seems like a pretty rare thing.
Although to be fair, how many IT people actually tinker at home in a way that impacts others? Most people need very little beyond their network and wireless working. Sadly very few IT people seem to care about even tinkering at that level that I've seen
-
-
@scottalanmiller said:
@Carnival-Boy said:
I think it's the other way round. In households where one person is tech savvy there is a tendency to tinker, fiddle, experiment and ultimately break things. The non-IT person then has to either wait for it to be fixed, or give up waiting and fix it his/herself.
How often do you think, though, that an IT person will break something beyond the point of them being able to fix it and then the non-IT person can just "figure it out?" Seems like a pretty rare thing.
Although to be fair, how many IT people actually tinker at home in a way that impacts others? Most people need very little beyond their network and wireless working. Sadly very few IT people seem to care about even tinkering at that level that I've seen
Coming from the guy whose home network is always saturated with issues... lol
-
@art_of_shred said:
@scottalanmiller said:
@Carnival-Boy said:
I think it's the other way round. In households where one person is tech savvy there is a tendency to tinker, fiddle, experiment and ultimately break things. The non-IT person then has to either wait for it to be fixed, or give up waiting and fix it his/herself.
How often do you think, though, that an IT person will break something beyond the point of them being able to fix it and then the non-IT person can just "figure it out?" Seems like a pretty rare thing.
Although to be fair, how many IT people actually tinker at home in a way that impacts others? Most people need very little beyond their network and wireless working. Sadly very few IT people seem to care about even tinkering at that level that I've seen
Coming from the guy whose home network is always saturated with issues... lol
Because I actually constantly test new gear and stuff. Which few people tend to do.
-
Yeah, I'll stick with a network that just works.
-
I used to test things all the time, but I did try to do it on a different segment so the rest of the house worked as normal.
-
I will break anyone's fingers that tests in my day to day environment. That get's done in a lab situation or on something that I don't use
