Unfortunately, that is neither the explicit statement, nor immediately clear to many readers. Taken as presented, many developers would assume they needed to suppress error messages.
I'm with you, while I can definitely see how someone could get the impression.
But the first thing I thought when I read this was that you need to plan for error states, but seriously attempt to avoid them.
While yes, as others have stated, users need to see errors when it's input or usage related, but the proper understanding of this quote applies there too. Because if the gui/interaction were designed properly, users wouldn't err. (some will always error, some are just dumb, others will try to break stuff on purpose.) there's no way to avoid all user errors, but you can definitely write code to account for all internal errors.
Its not about suppression, it's about prevention.
I'd say the fact that yours is the fourth interpretation of the quote in this thread shows my entire point about the lack of clarity in the quote. ;)
With that said, I do agree with your position wholeheartedly, especially as it relates to a GUI.
Allow me to submit what may be a clearer alternative to the quote in question (although I'm hardly well-known enough to be quotable in my own right)...
Instead of writing better error messages, write better code that doesn't necessitate error messages.
Silicon Forest Developer/hacker. I write about Generative AI, DevOps, and Linux mostly.
Once held the world record for being the youngest person alive.
Unfortunately, that is neither the explicit statement, nor immediately clear to many readers. Taken as presented, many developers would assume they needed to suppress error messages.
I don't agree
I'm with you, while I can definitely see how someone could get the impression.
But the first thing I thought when I read this was that you need to plan for error states, but seriously attempt to avoid them.
While yes, as others have stated, users need to see errors when it's input or usage related, but the proper understanding of this quote applies there too. Because if the gui/interaction were designed properly, users wouldn't err. (some will always error, some are just dumb, others will try to break stuff on purpose.) there's no way to avoid all user errors, but you can definitely write code to account for all internal errors.
Its not about suppression, it's about prevention.
I'd say the fact that yours is the fourth interpretation of the quote in this thread shows my entire point about the lack of clarity in the quote. ;)
With that said, I do agree with your position wholeheartedly, especially as it relates to a GUI.
Allow me to submit what may be a clearer alternative to the quote in question (although I'm hardly well-known enough to be quotable in my own right)...
Well said! But while clearer, it doesn't quite a have the same ring ;)
As a professional author, allow me to assert: clarity is better than brevity; but if you can get both, do.
Now that's got a ring to it.
Shrugs What can I say? You win some, you lose some.
Trying again...
I like this better than the original.