The worst exception handling
After I’ve finished writing the last post and tried to hit “Post” – BlogJet has pondered a little bit and then popped up window saying “Something has went wrong”.
Well, that’s how you should never write your exception messages (if they ever show up). People do not seem to appreciate when something suddenly goes wrong. It is better for us to see the exact problem and the actions that could be taken to deal with it.
And if the exception/problem takes place for the first time (and thus the application could not tell how to deal with it), then that is one more bug to score. Prompting user with the dialog to review and send the exception details to the issue management system – is the best way to capture it while it is fresh.
People at JetBrains do it all the time. And the people were praising them in weblogs for that (especially when they were contacted back in a couple of hours after submitting some new exception).
No comments yet.
Leave a comment
Search
Archives
Recent Comments
- aCoder on Extension methods for interfaces
- Requirements for the Photon .NET project | Rinat Abdullin on IRepository, cross-cutting concerns and flexibility
- Nicholas Blumhardt on Extension methods for interfaces
- aCoder on IRepository, cross-cutting concerns and flexibility
- Rinat Abdullin on Blog upgraded
- Rinat Abdullin on Extension methods for interfaces
- IRepository, cross-cutting concerns and flexibility | Rinat Abdullin on Extension methods for interfaces
- Bill Pierce on Blog upgraded
- aCoder on Extension methods for interfaces