undefined | Better HN

0 pointsmegaman228y ago0 comments

> e.g. programmers do magic things like read the error messages on the screen. Non-programmers not only don't do that, they can't comprehend why it's necessary. (Without exaggerating too much)

More than once it has crossed my mind that it would be worthwhile to build custom error message dialogs that can't be closed for at least 30 seconds (maybe with a secret override) for some areas of our products. The number of times I've been on a support screenshare with customers where they try to connect to some external service, and it fails, and they instantly dismiss the prompt that would tell them exactly why it failed, if they would just read it, is maddening. At least that kind of a built-in delay would give me time to fire up the snipping tool and grab a screenshot from my end...

0 comments

icebraining8y ago

Why not just write to an error log? You could even have some button to send it to you or something.

megaman22OP8y ago

Oh, we do that too... It's a struggle to get people to actually send those to us, for some reason, or even just open them up. Usually this kind of thing occurs with initial installation, and we're typically installing into some location that is firewalled to hell and gone, so we can't depend on being able to access anything even within their own LAN, let alone the outside internet.

Enterprise Windows software is so much fun.

j / k navigate · click thread line to collapse