NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Oh what fun!
More |
Login
| Reply
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
about I/O disciplines and I should retire to the Tassili-in-Aijer
mountains in Sahara as a camel herder :-)
-- Jarkko Hietaniemi
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Creative Error Messages (Score:1)
"You want me to do WHAT!?!?!"
"HAHAHAHAH!!!"
"Oh man, you are SO screwed"
"Once again, this time with feeling!"
"Oh dear god what a clusterfuck, I honestly don't know where to start even describing it
Contingency Design (Score:1)
Designing error messages (and how programs act upon failure) is contingency design, and it's really a UI problem. Like most UI, it's harder than you'd think to do really well. The user needs to know in plain language what went wrong, what caused it, and what they can do about it.
There used to be a nice collection of good and bad error usability examples called Design Not Found, but it seems to have been replaced by a link to a book [37signals.com]. I was able to find an archive of the site [archive.org], but it suffers from some missi