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
Error _system_ (AI-based)
Replying to @gdb
Like the f’n engine light coming on because of a Gas Cap sensor. Takes 3-4 visits for the technician to figure it out.
Replying to @gdb
How about just a good clear and exact explanation of what went wrong? Going overboard with error messages is tantamount to documenting and commenting everything. Good code explains itself. Good errors messages should need no addendums
Replying to @gdb
wrr, no l, hx about it, no nerx, ts just a toolx
Replying to @gdb
First I am a crap programmer. Second I suck at it. Third. What he just said. ☝️ I use software I am not Tesla. If you get what mean.
Replying to @gdb
I'm missing the olden days of error numbers. They may look like a UX nightmare but you can take a number and look it up online and in the manual. Error messages are messy. A reason I (a German) uses many programs in English is so I can look error messages up online.