Beefy Boxes and Bandwidth Generously Provided by pair Networks
Think about Loose Coupling

Re: Error handling - how much/where/how?

by Joe_Cullity (Beadle)
on Jun 13, 2005 at 16:21 UTC ( #466208=note: print w/replies, xml ) Need Help??

in reply to Error handling - how much/where/how?

IMHO Ė The amount of error processing really depend on where what and when.

If the program is a simple batch job that runs at 2:00am, can be re-run if it fails and the output wonít be used till 9:00am in the morning, then maybe you can scrimp a bit on the error handling/reporting (But I bet after a few years of frantic 2:00am phone calls, you might change your mind.).

If itís a heavily used data entry screen thatís expected to protect the integrity of a production system from invalid data , then Iíd do a bunch more error checking, input validation, and reporting in human readable format (Like ďZip Code must be in the format of NNNNN-NNNN).

If the system handles 80% of the crude oil transactions in America in a real time highly visible environment, or monitors the pressure of a 747ís flaps as they extend down for landing, or perhaps handles the collision avoidance subsystem of a robotically controlled blood analyzer as strings of small glass veils containing potentially contagious sample whirl byÖ. I donít think any amount of error handling/reporting is too much.

After 35 years of people wakening me up at 2:00am because a downstream job failed due to my program missing an opportunity to report bad (or just perhaps very unusual) data, youíll find that I put as much error catching/reporting code as possible into every program I write, and lots more into the critical ones.

  • Comment on Re: Error handling - how much/where/how?

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://466208]
and the leaves swirl about...

How do I use this? | Other CB clients
Other Users?
Others musing on the Monastery: (4)
As of 2018-05-20 17:54 GMT
Find Nodes?
    Voting Booth?