UX: Is it better to ignore errors or fail loudly?

This question came up in a discussion I was having with my co-worker Chris Brewer. Suppose /foo is valid, but the user asks for /foo/bar. Should we just show /foo, or show a 404?

In other words, which is better: being nice or failing loudly?

Superficial love or tough love?

Arguments for the former: Postel's Law. Null Object pattern.

Arguments for the latter: Throwing exceptions. Fail loudly.

comments powered by Disqus

Did you know?

I'm a software engineering consultant. This means I can help your company with your software engineering needs:

  • providing temporary manpower for short-staffed software projects

  • helping new software projects get off to a good architectural start

  • improving the performance and reliability of old, legacy software systems

  • doing an important investigation or small project that you've always wanted to do but haven't had time for

Since 1999, I have done software engineering projects for the Canadian government, for Silicon Valley startups, and for established Bay Area companies, for small companies and medium-sized companies, for successful commercial projects and open-source projects. 

Currently accepting small projects. If you have one, email or call me.