Banking Online Usability Fail
Back in college, when I first started handling "exceptions" in my programming, I used to sometimes get it wrong and use a handler that was too general on the outside of the method and it would catch any and all exceptions thrown before specific handlers inside the method could act. This led to some rather wooly error messages, like "You fail, you n00b!" I soon realised how to deal with exceptions correctly however and any exceptions thrown at runtime became clear.
It now appears that I was wrong however. In the real world of business, nobody goes into detail when handling errors. In fact, I think the above pic probably illustrates a very generous amount of detail of the problem encountered: It was a problem with the "digital certificate" after all. Oh hurrah, I should feel so lucky that it wasn't just "a problem" with the whole system that I had to figure out. Well I'm counting my fucking blessings right now...
Posted at 12:47