Recent Posts
Recent Comments
- python – Testing email sending-ThrowExceptions – ThrowExceptions on PostHoc: Testing Apps that Send Email
- The Silent Enemy: Failure to Report Exceptions | Thinking Matters on The Purpose of Error Reporting
- Colin James III (The Most Rev'd, Ret.) on Not-So-EasyChair Hints
- gizmos and gadgets on The Only Class You Need for CSV Files
- kswenson on The Only Class You Need for CSV Files
Archives
- May 2021
- April 2021
- February 2021
- December 2020
- April 2020
- February 2020
- November 2019
- October 2019
- June 2019
- May 2019
- February 2019
- January 2019
- November 2018
- June 2018
- May 2018
- April 2018
- February 2018
- January 2018
- December 2017
- November 2017
- July 2017
- June 2017
- May 2017
- March 2017
- January 2017
- June 2016
- March 2016
- February 2016
- December 2015
- November 2015
- October 2015
- September 2015
- August 2015
- June 2015
- April 2015
- January 2015
- November 2014
- October 2014
- September 2014
- July 2014
- May 2014
- April 2014
- February 2014
- January 2014
- October 2013
- August 2013
- July 2013
- June 2013
- May 2013
- April 2013
- March 2013
- February 2013
- January 2013
- December 2012
- November 2012
- October 2012
- August 2012
- July 2012
- June 2012
- May 2012
- April 2012
- March 2012
- February 2012
- January 2012
- December 2011
- November 2011
- October 2011
- September 2011
Meta
Tag Archives: errors
Is Non-existence an Error?
You call a method to retrieve information about an object with a particular ID, but the record does not exist. Is this an exception? Or not? It is hard to answer.
Two Kinds of Exceptions
An exception is a message from the system to the user about something that the program can not handle. There are a couple of main categories of exceptions: environmental and program logic. They warrant quite different treatment.
Posted in Coding, Design, Poor Error Msg, practice Tagged code style, errors, exceptions, program logic error, usability Leave a comment
Error messages should be very literal
We all struggle with the correct wording for error messages. It is not easy. But I ran across an example today that should help understanding
Error-First Design in JSON/REST/AngularJS integration
You have heard about “mobile-first” when creating your UI, but there is something you should do before you start designing the UI: you should design the error handling/display mechanism first.
"Oops something failed" is NOT acceptable error message
I try to keep track of real-life situations where poor error messages appear. That happened again today. This message was displayed to the user:
Robust Web Application Initialization
When a web based application starts up, it should do so carefully to avoid a number of problems. This post outlines the problems you might run into, and a list of coding preparations that can be made to avoid these … Continue reading
Posted in Coding Tagged configuration, design, errors, exceptions, initialization, robustness Leave a comment
Error Message should be clear, plain, and direct
This post is about a real error message I received and puzzled through. Luckily, because I was working with open source code, I was able to see a copy of the source, and only then did I understand what the … Continue reading
Posted in Coding, Example Code, Poor Error Msg Tagged design, development, errors, exceptions 2 Comments
Surprising outrageous file handling
I don’t usually focus on bad examples of code (because there are so many ways to do it wrong they are rarely repeated) but here I found a particular pattern that was pernicious and repeated all through the code, indicating … Continue reading
Usability Means Not Jumping Through Hoops
The image of being forced to jump through hoops is one of being required to take arbitrary actions in arbitrary orders just to satisfy some goals that are either unseen or at least not in the interest of the user. … Continue reading