One of the least-appreciated skills in programming is writing anti-frustrating error messages. A good error message should make it self-evident (a) what the user did, (b) what acceptable inputs are, and (c) how to fix the problem. Can determine love or hate for your library.

Feb 22, 2022 · 4:24 PM UTC

245
663
50
8,979
Replying to @gdb
Or do what most devs do... Throw(E_FAIL)
Replying to @gdb
I am really excited .Waiting for Bugs. Lets see how much ...
Replying to @gdb
I think people do otherwise to become impresscindible and they become hated indeed.
Replying to @gdb
[object Object]
Replying to @gdb
I like those points. It's best when the message includes the element &/or 'operation' it was trying and what value it was using. Impossible condition error messages should be extra clear because they happen all the time during alpha test...
Replying to @gdb
It would be great if someone with control of excel programming soaked this in… The most unhelpful error messages every single time