And lest you think this is just end users and non-tech people: I have gotten the same sort of responses from system admins for major companies when I try to walk them through something.
I’d argue that most people, including the ones who administer systems, don’t know how computers work. They’ve learned some things by rote, sure, but beyond that they’re helpless.
Oh, but we haven’t talked about the opposite thing, which is when tech-savvy user X thinks they know better than whichever IT person or team set up a process and decide to ignore it or bypass it and then they break something and nobody’s happy.
I see your point, though. I mean, even if you know what you’re doing there are many times where you just need to get a thing done and you just want somebody to make it so the computer does the thing, rather than understand how the thing-doing is done. We forget, but computers are actually super hard and software is overcomplicated and it’s honestly a miracle most of it works at all most of the time.
The folks who know enough to know they need processes aren’t the problem. If you give them instructions they’ll follow them and things will be okay.
It’s the folks who don’t know that they need processes who are the problem. The folks who, after having walked them through something ten times, ask you to do it. They see an error message like “TCP connection timeout” and have no idea where to start looking, except to send me an email so I can tell them that they probably have network issues.
I agree: The fact that it works at all is astounding.
