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
[爱心][爱心][爱心]$DOD was invited by Btok to promote DOD in the Telegraph group on 26th DOD project and all the holders are cordially invited to you
Replying to @gdb
I LITERALLY CAN'T WAIT TO USE THIS PLATFORM
Replying to @gdb
So true
Replying to @gdb
Current practice for error messages seems to be, "An error occurred. Bye."
Replying to @gdb
If I ever write a library I am going to intentionally make vague and incomprehensible error messages because I like to see the world burn
Replying to @gdb
BTOK is the chat software I often use, and our token $DOD is going to do AMA video conference in the official group 14 tonight.