3 ms·
I initially attributed this kind of omission as originating from laziness or just not knowing how to copy-and-paste* into their email client. Now I think it act
by danso 12y ago
I initially attributed this kind of omission as originating from laziness or just not knowing how to copy-and-paste* into their email client. Now I think it actually stems from a much bigger problem: the average computer user's inability to understand cause-and-effect, and their belief that there is just "the error", with a corresponding "the solution", because they think there is only one reason (and not really a real "reason", as it seems to be only understood by "neckbeards") that a computer error could occur.
Thus, it's not laziness, just something that logically follows from the erroneous assumption that there is only one kind of error, and thus, a competent programmer should automatically know the one solution to it.
* In terms of people not being able to copy-and-paste...just because they can do it in Word doesn't mean they realize that function exists in other apps. Take Google's finding that 90% of users didn't know how to use Ctrl-F (http://www.theatlantic.com/technology/archive/2011/08/crazy-90-percent-of-people-dont-know-how-to-use-ctrl-f/243840/ http://www.theatlantic.com/technology/archive/2011/08/crazy-...)....just a couple days ago, in the final week of my programming class, one of my students was amazed when I did a Ctrl-F in the terminal.
- epriest 12y agoI originally wrote this when I worked at Facebook. The intended audience (who were submitting these reports at the time) was professional software engineers.
- sitharus 12y agoAs a professional software engineer I can confirm that many of our rank have some sort of blind spot when it comes to error messages. Many time someone has commented "I don't know why this build is failing!", and a quick search for "Error" in the build log reveals the exact cause. My current pet peeve is an error message that reads "This application requires <dependency A>. <Dependency A> can be installed from <url>". If I had $1 for every time someone said "I don't know how to fix this".
- wodenokoto 12y agoThat's quite funny. I read the headline and thought "OMG, nobody at HN needs to hear that message, comeon!"
- thehoff 12y agoInteresting thought. In many cases I've had its the first case (not knowing how to copy and paste). But this reasoning makes a lot of sense for the ones I get from people that definitely know copy-and-paste. For these folks, I get a screenshot and/or text of the error but still the "its broken" without much else.
- aaronbasssett 12y agoI…I…I never even thought of using CMD+F in the terminal. It just never occurred to me. CTRL+R, sure. But not CMD+F. ~Two decades of scrolling back through hundreds of lines looking for a single piece of output. Well now don't I feel like an idiot.
- Raphmedia 12y agoOh my god. You are not alone.
- s_kilk 12y agoAnother possible factor: some people suffer from a kind of "error blindness", when the computer shows them some text, even really simple text, they don't seem to be able to see it, almost like their optic nerve is censoring the text. You can write your program so that on error it shows a message like: "Push the red button" ... and many users will just stare at the screen and proclaim "I don't know what to do, what's wrong with it? How do I get back to the thing?"
- JoeAltmaier 12y agoThat may be the 'cry wolf' thing. There are so many pointless dialogs pushed into your face, you stop reading them. Install any package, and pound on 'Next' until the damn thing finishes installing. We're trained to ignore them in this way.
- hobarrera 12y agoNot sure what terminal you're using, but CTRL+F on a terminal is pretty non-stadard. I wanted to make sure it's not me who's using the terminal that's different, but it's not the case, bash's doc state that "Ctrl+F: Forward one character".