Beefy Boxes and Bandwidth Generously Provided by pair Networks
Keep It Simple, Stupid

Re: Defensive Programming and Audit Trails

by tmiklas (Hermit)
on Aug 06, 2002 at 10:48 UTC ( #187979=note: print w/replies, xml ) Need Help??

in reply to Defensive Programming and Audit Trails

In my oppinion, the larger your code is, the more places for it to fail.
I know that describing exceptions takes time - even more than to write 'working' solution, but... if something fails, you should be able to find (immediatelly) what, where and when has failed. Whenever possible I check return codes of functions and calls and log all errors to a file/syslog/whatever. During developement you can log every single error, eg. missing parameters, etc. (of course for developement you don't use any sensitive data). On working systems you should log all exceptions and failures, where 'all' means enough for you to know exactly what failed, but not enough for others do compromise data your software is work with.

BTW. Another rule says that the less you know, the better you sleep but that doesn't apply to programmers ;-)

Greetz, Tom.
  • Comment on Re: Defensive Programming and Audit Trails

Log In?

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://187979]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others perusing the Monastery: (4)
As of 2022-05-28 02:28 GMT
Find Nodes?
    Voting Booth?
    Do you prefer to work remotely?

    Results (98 votes). Check out past polls.