burkphoto wrote:
You can learn TO do something, but when it doesn't work right, you must know WHY and HOW it is supposed to work, at least well enough to know WHAT to do next.
I've always hated Microsoft's "technically correct, but functionally useless to real users" error messages. They assume you are as knowledgeable as the developers. My favorite was something like, "Unimplemented Trap". Hell, it seems like a trap to me! Why am I here, and how do I avoid getting here again? Who can I reach out and grill for answers?
I've always thought that error messages should say something honest, like, "We didn't anticipate that this could happen! You have to restart the program. Sorry you may have lost some data." Don't just leave the poor user without a map out of the jungle. Throw 'em a lifeline.
Do this step: [action]
After: [previous action]
With: [tools, supplies, information...]
Because: [why, purpose...]
Before: [next step]
Expected Result: [desired outcome]
Other Possible Outcomes: [failures]
Failure Remedies: [try this, that, or something else...]
I remember Bob and "Clippy," the dancing paperclip with useless advice that stole all my system resources.
You can learn TO do something, but when it doesn't... (
show quote)
Maybe AI will fix this problem. There is certainly not much hope of real intelligence helping out here. Not that the programmers aren't intelligent, but they are hobbled by lawyers and managers.