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
664
50
8,978
Load newest
Replying to @gdb
You have not lived till you learn to read a COBAL dump. coders today have it so easy.
Replying to @gdb
Just write code that doesn’t error. :p
Replying to @gdb
@gdb the digital world needed you 25 years ago. Few could understand that then.
Replying to @gdb
Yah! When ever I make a mistake it's the user's fault! Godam users, if they'd only hit d' keys n' buttons they're supposed to this job 'id b so much easier. Oh, I mean when ever "they" make a mistake it's their fault. My code if #ucking perfect. 100% 😂🙃🤣😂
Replying to @gdb
Hmm... "Bad magic number"
Replying to @gdb
Si desde un comienzo se tienen claras las necesidades del usuario y se diseña un proceso eficiente se reduce los errores y la mayor frustración no está en la aparición d estos sino en el tiempo perdido
Replying to @gdb
True, all programmers accept it.
Replying to @gdb
nitter.vloup.ch/CryptoInu_ABCD/s… b
Crypto Inu 🇺🇦 @CryptoInu_ABCD
21 Feb 2022
#CryptoInu Date: 23rd Feb 2022 (Wednesday) *Our First Big Milestone to be announce." #dogecoin #metaverse
Replying to @gdb
“Something went wrong” is my favourite #Microsoft
Replying to @gdb
What you just did: told us you don’t work for Microsoft without telling us you don’t work for Microsoft. To be fair, you also told us you don’t work for Apple.
Load more