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, doas 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.
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.
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.I don’t need to make sense of error messages. Which is good because I usually can’t.
I just need them copy/pasteable cuz that shit is going in Google and I’d rather not manually type it.
It’s not even obscure, context dependent errors. I’ve had many professional system administrators not understand what “connection was closed by peer” meant.
Well, to be fair, I’m also not very well versed in the intricacies of connecting with British nobility.
One day I’ll catch that jerk Peer! So rude, always closing my connections!
More than once I had trouble calls about an “error message” that basically said “everything is fine, click ok to proceed”
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.