Paranoid Programming

Hey guys, I just saw The Bourne Trilogy and I want to know how to become a paranoid programmer.

OH GOD A BUG WHAT SHOULD I DO THERE'S A BUG IN MY PROGRAM.
WHAT COULD IT BE? M-MAYBE THAT MALLOC? I DON'T KNOW! I... I DON'T KNOW WHAT TO DO. OH GOD, I'M LOST, WHAT SHOULD I DO? GOD, PLEASE, TELL ME! TELL ME!!

The easiest way to become a paranoid programmer is to assume anything can fail (yes, even that innocuous d = d * -1;) and bring the whole application crashing down.  Once you're in that mindset, begin writing conditions to survive a failure of all offending lines of code.  And then write conditions to survive the failure conditions failing.  If you need to go any further, you may as well give up programming and take up poetry.

>>3
d = INT_MIN;

>>1
become a paranoid programmer and you will be happier

http://en.wikipedia.org/wiki/Test-driven_development

unless you are a lone freelancer

>>4
What if there's a bug in the standard library?
And what if it runs out of space and it can't be allocated on the stack?
And what if the user tries to shutdown the system while d is being assigned?