4 ms·
This post does put the finger on one widespread problem: Bad error messages. When you're designing an error message, don't just tell the user that something we
by tempodox 6y ago
This post does put the finger on one widespread problem: Bad error messages.
When you're designing an error message, don't just tell the user that something went wrong. The mere fact that they're getting an error message already conveys that. Instead, concentrate on telling them what is being expected or what they can do to fix it.
- catlifeonmars 6y agoTotally agree! I have to say, as an author of preprocessor/compiler toolchains, I’ve struggled a lot with designing error reporting in a way that maintains abstractions in the toolchains, but still produces useful error messages. Oftentimes, I’ve fallen back to hard coding error messages that assume a particular code path. I’d be really interested in seeing examples of error reporting patterns that work well across multiple levels of abstraction.