Publication Date: 1/18/2009 10:00:18 PM
One of my customers has a web application that uses the out-of-the-box exception handling instead of a custom error page. So every time a user encounters an error, they see information that is useful to the developer, but isn't understandable by the end-user. There are several reasons why this is a bad practice:
One of the ways that programmers cut corners is to skimp on effective exception handling. In some cases it may be acceptable to take on the risks of using the default exception handling, but in many cases this is a bad idea. If you encounter errors in your software that aren't very user-friendly, you should raise the issue with your programmer, especially if the errors seem to include details that might pose a security risk.
Think like a geek
Your URL (optional):
Type the code shown
Top 5 Programmers to Avoid
What everyone should know about bugs
How to tell if an estimate sucks
The Secret to Building a Crappy User Interface
The Problem with Selecting the Lowest Bidder
5 Ways to Control Software Development Costs
Avonelle is a talented expert in her field. She has blended well with our team and built applications that we are proud to deploy to our associates. Her talents helped us execute a vision expediently and with quality. If we could do it all over again, we wouldn’t change a thing.
Peter Edstrom @ Renewal by Andersen
Copyright © 2013 Avonelle Lovhaug. All Rights Reserved.
Sitefinity ASP.NET CMS