>decide if the cost of dealing with it is greater than the cost of preventing it Yes. I build small apps for various tasks at my current job and am always surp

>decide if the cost of dealing with it is greater than the cost of preventing it Yes. I build small apps for various tasks at my current job and am always surprised at how bullet proof they want the thing to be. I spend the majority of my time trying to safely handle the remotest of issues for these apps which are mostly fairly trivial (not operationally critical) if they stop working. I find it especially amusing because we host our entire operation off a single box in our own network closet. In other words, make sure you take care of all the simple things that have a much higher chance for disruptive error before you start worrying about the once in a lifetime catastrophic ones.