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
Sorry something went wrong goodbye is my least favorite message
Replying to @gdb
Where's the delicious cheese sandwich?
Replying to @gdb
Yes
Replying to @gdb
Don't forget to put an exclamation mark when logging errors!!! This trick will guarantee a constant stress for those involved with fixing problems.
Replying to @gdb
All api errors should contain some sort of 'message' property at a minimum
Replying to @gdb
of short answer, response more so stench'ism 'estech grab
Replying to @gdb
"Hello dear. You made a little, little mistake. Please try again using ...". "Hi. Fifth time you make this mistake. Last warning." "He you - you are too stupid for this program. Will shut you down forever now. No credits this month."
Replying to @gdb
Humans are just A.I. with good ass error messages. Change my mind. @lexfridman @elonmusk