This cannot be overstated.
Every time I review error messages, I _always_ ask 3 things:
- What: is the "what" clear.
- Why: explain the reason this happened.
- Next: what can be done next.
Almost all error messages can be expressed this way (the exception being the ones about security where giving information is a way for attackers to more about users, etc.)
The result is great: users almost never ask you any questions, and when they do, it usually means it's either because the message told them to, or because the error message is not clear, and we ensure to clarify it.
Re:Long Error Messages
by logbiscuitswave on Thursday September 23, 2021 @12:32AM
(#28625238)
I agree fully with this. Sadly it seems like entirely too much software these days has pivoted to the essentially useless “oops something went wrong” error messages.
For an average end user...
* If the hard disk is full, that's easy to convey and easy to suggest a fix.
* If a hardware fault occurs on activating a device, suggest they try again and contact support if the problem persists.
* If an unhandled exception occurs, all they need to know is that something very unexpected happened, and they should contact support - they don't need to see a stack trace and error message.