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
I remember when all software feedback was valuable!
Replying to @gdb
@elonmusk if your product are eye catchy then though after 100% of import duty your product will become hit in India, and if your product isn't good then though after 40% of import duty your product will become flop .learn something from tata punch as its overpriced but is a hit
Replying to @gdb
Catch(error){ Console.log(error.message) }
Replying to @gdb
A clear exception is when giving error messages for authentication or authorization be careful the information you give to avoid helping an attacker pwn your system.
Replying to @gdb
Don’t care to
Replying to @gdb
Yes. Take a look at Elm on how to do it right.
Replying to @gdb
Yes! I think the hard part is modeling a reader with much less information/understanding than the author at time of writing the error. In particular including reader=author+{6 months}
Replying to @gdb
Wkam
Replying to @gdb
placing and accumulating all application related custom error code + messages in tables will bring uniformity. once a certain application error occurs lookup by code and get message string from table and throw exception. add some error string to exception if need be.
Replying to @gdb
Katanya banyak gunakan Rust ya.. padahal c & python cukup relevan kok
Load more