Forums
Learning to handle exceptions properly, knowing when to catch, and when to throw them, is an art. Knowing when it’s a case to retry or to abort a process requires a deep understanding of the problem you’re going to solve.
This code, which Adam found, is a pretty bad example of what to do:
The ICSP compliance application was a dull piece of software. Instead of managing Active Directory with one of the many off-the-shelf packages, this was built in-house, and helped the sysadmins manage user accounts, permissions and access. Despite the fact that this application had no right to exist, it did, and it was tied into so many IT business processes that ICSP was marked a “critical” application.
Kelly spent too much time with her hands deep in the entrails of this ugly creature. Since she “owned” it, she was the recipient of a panicked email: “ICSP is down! What did you do?” She had changed a few things is code, recently, but nothing had been released to test, let alone production. Quickly, she skimmed the email chain.
Feb 14