Who is this "user" you speak of? :-)
I'd extend that a bit for batch systems: invoke some kind of tool to file a trouble ticket to get the operations/support group's attention, as there won't be somebody sitting at a console to watch. Alternately, you could view this as generating a big red screen, just realize that any users are sitting "someplace else".
Yeah, some of us still have batch operations going, as well as a web app or two.
Re:A Manifesto For Error Reporting
by HeyLaughingBoy on Tuesday March 05, 2013 @10:11AM
(#5324841)
There's a third thing to consider: how to recover from the error. In many cases, the recovery is something the software has to do itself: e.g., server down, switch to alternate server.
My preference is to consider error reporting as something completely separate from error handling. This is even more the case if you have different classes of users.
all well, but that 3rd one highly depends on context. If I have an application for collecting/analysing data that is going to be used to publish papers and whatnot, it is absolutely critical the algorythms I write are ok no matter what. If they are not, it's time to go berserk (as in the 1st one). Ignoring it would be the worst I can do at that point.
- What should I do here to help me and other developers understand what's gone wrong. This generally results in one of the three categories:
- What should I show to my user. Divided in three categories too: