Wednesday, December 14, 2011

Why do people have such trouble with error messages

So a colleague of mine took a call from a user who got a “cannot open file located in <path>” error. This person asked “what could it mean”. This begs the question of why this person didn’t immediately just go to the path and see if the file existed. I just responded to someone who got an error “cannot create project in directory <path> because a project already exists in that location”. Once again, the user asked “what could that mean”. Now, given that the error messages actually tells you “here’s where the problem lies” why on Earth would someone not just go and put eyes on the issue? What is it about error messages that computer professionals have trouble with “look, go here, the problem exists at this location”?



No comments: