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
Under-appreciated corollary -- Never use (Yes/No) or (OK/Cancel) buttons when you can name the buttons for the exact action. Fewer errors and a vastly lower cognitive load for users.
3
6
1
111
Replying to @gdb
馃憤馃徏馃憤馃徏馃憤馃徏
1
Replying to @gdb
Instructional design for the win! 馃憤
2
Replying to @gdb
I am going to follow you for my own reasons, even though you don鈥檛 follow Miley Cyrus.
1
Replying to @gdb
Tell that to Autodesk
2
Replying to @gdb
So true, I wish other IDE can tell me my mistakes like 馃憞
3
Replying to @gdb
Somebody, please send this to everyone that thinks a, "General Fault found in 0x0000037464748364637282Y464UE8EYDBDH," is helpful. It isn't. Not even to tech support.
1
Replying to @gdb
Yes, this is UX writing an often neglected component, in the development of digital products
1
Load more