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
Load newest
Replying to @gdb
Is there an end to it? Why can’t it fix a error message by itself instead of throwing an error
1
2
Replying to @gdb
As a retired programmer with 45 years under my belt, I always requested that I talk directly to the end user.,I didn't always get to, but things were better when I did.
2
Replying to @gdb
1
GIF
Replying to @gdb
Errors are like pokemons, you need to catch them all 😅
1
Replying to @gdb
Une rédaction de notice d’emploi, message d’erreur. Un beau challenge pour le constructeur. Être clair, accessible à tous , la tâche n’est pas simple. Y parvenir c’est une belle victoire et une valeur ajoutée énorme apportée à son produit.
2
Replying to @gdb
Part c: nothing as glorious as getting instruction on how to fix a problem. Far too rare.
2
Replying to @gdb
Better still…
5
Replying to @gdb
C# "You did something here, and this is what you did." Swift "Lmfao it's an error, it can mean 1001 things. Now go fuck yourself"
3
Replying to @gdb
so this would be 'bad' ? A error:you're a dummy B error:try typing it correctly, you dummy C error: i know that second line is third answer YOU made me, GIGO ... you dummy. ? try ctrl+alt+delete emergency boot repair disk use linux(it's free) play more how to type words game ?
1
1
Replying to @gdb
“We have encountered an error. Please try again later” 😬
1
2
Load more