You must log in or # to comment.
Most people don’t even read the error messages. They’re never gonna read a whole manual.
Most people were conditioned by more “user-friendly” systems to ignore the content of error messages because only an expert can make sense of “Error: 0x8000000F Unknown Error”. So they don’t even try, and that’s how they put themselves in a
Yes, do as I say!situation.It’s not even obscure, context dependent errors. I’ve had many professional system administrators not understand what “connection was closed by peer” meant.
One day I’ll catch that jerk Peer! So rude, always closing my connections!
Well, to be fair, I’m also not very well versed in the intricacies of connecting with British nobility.
But most error messages are in plain English first (plus some numbers and codes).
No, they see white (gray actually) blocky text on a black background, they think the machine is broken and go into panic mode. Instead of reading.
Which is kinda what you said.
People who don’t read error messages or do not take the time to see what is going on and just come to the technician/mechanic/doctor saying “it doesn’t work” or some half-assed hypothesis piss me off so bad.
I know that at some point we all do a little of this in our lifes, but some people don’t seem to be able to read one goddamn paragraph ever.
but some people don’t seem to be able to read one goddamn paragraph ever.
I had a problem with my car. It felt strange while driving. Made some unusual noise. Then a bit later the motor warning light came on.
I went to the garage, told them about the warning light and what I noticed the time before, what I suspected and such. A short while after the mechanic came to me and asked for a few details, as my description “wasn’t helpful” and the repair would be much faster with more details that told them where to look etc. Turns out the guy who checked in my car only noted “a warning light is on” and nothing else of my ramblings.
So sometimes it’s also paying attention to what might be important and relaying information.
ah well, then that is them being stubborn and being unable to troubleshoot.
To be fair, I forgot an important bit of context. I was on vacation abroad when my car broke on a Friday afternoon. Our hotel room was only available until Saturday morning as everything was booked out for the weekend because of a huge event in the city. They asked me just to get a first indication and not waste time with random troubleshooting, so that I could get home and get everything checked completely with a more relaxed schedule.
From my view, it was a sensible thing to do. But the literal translation on their report they showed me was just “the warning light is lit” - not even which (though that is quite obvious, when you start the engine)
To be fair, techs don’t usually talk to the people who can read, so they’re only ever going to see idiots. There are competent people in the world, they’ll just never need your help, so you don’t see them.
Last time I called tech support, it was for a Dell, and I interrupted their speech to tell them I already looked up the diagnostic. They asked which numbers were lit on the error panel to confirm I had the right diagnostic, and passed me directly to who I needed to talk to. I only called tech support because the cpu socket died and I was putting in a warranty claim, otherwise they would have never even heard from me because I could just install a new motherboard myself.
edit: speeling
THIS. The people who actually read the error messages aren’t going to stop there, they’re going to look up said error message, find a solution on their own, and continue with their day without having to interact with another human.
