3 ms·
I enjoyed the read (but it isn't really the type of article I usually come here to read. It seems to be something that may be better served in a management or p
by ChrisMarshallNY 6y ago
I enjoyed the read (but it isn't really the type of article I usually come here to read. It seems to be something that may be better served in a management or personal improvement venue). It's a bit disappointing to see it being treated so cynically, but that's really who we are, in this industry (wish it were different, but we need to accept the bad with the good).
> When a program stops working, do you face a baffling error message with no further guidance or clear instructions for how to get help?
Error handling is incredibly important to me.
Not just trapping errors, but also presenting them to the end-user. Masking technical details is quite important. Most engineers won't ever be informed that the error happened, so there's no reason to provide a core dump to the user. They just need to know that the program has encountered an anomaly, and how that affects the end user, at that moment. They need to be informed of the consequences of the error, and any possible mitigation.
Helping to remove the "emotional sting" from an error message is important. There was this excellent comedy routine, in the early 'oughts, called "Welcome to the Internet Help Desk"[0]. In it, the support rep encounters a user that breaks down in tears, when confronted by a fairly standard Microsoft error message.
I've found that the best way to resolve errors, is to not encounter them. This is accomplished by a combination of good programming, and good usability. Doing things like disabling or hiding paths that could lead to errors, developing a carefully-worded product glossary, etc.
[0] https://www.youtube.com/watch?v=nL24aNugo_4 https://www.youtube.com/watch?v=nL24aNugo_4