3 ms·

I generally agree with this, but making sure your error messages are correct is even more important than terseness. The last example of the article is a perfect

I generally agree with this, but making sure your error messages are correct is even more important than terseness. The last example of the article is a perfect illustration of this: $ cat invalid cat: invalid: invalid path An invalid path or a file not found are not the same thing! The real danger is that being too terse and unclear is worse than unnecessary verbosity.

majkinetor 6y ago
It should just have been File not found without anything else by the logic presented in the article. However, there are some problems with entire thinking: - When you are looking into results of larger set of operation (i.e. scripts) you may need more info to easier grasp the context - Did you see it already ? There is no need for verbosity once you experienced a problem recently (which is what happens most of the time) The errors deserve both variants, short and terse, just not on the same place (I don't want spams in terminal or logs). Short variant should provide some form of id that can be looked at for more details: cat(e123): file not found e123 could be searched in detailed error message document.