in reply to
Avoiding silly programming mistakes
I actually have advice for the OP! How cool is that?
I make D'oh! mistakes every two seconds. My best strategies involve reducing the opportunities for mistakes. In practice that mostly means code re-use. So, for instance, if you had based your object on a superclass that already did that job of destruction, you wouldn't have made that D'oh mistake. Or, in a less elegant but probably more applicable example, if you had taken an already existing class that included a destructor, gutted most of the code leaving a class skeleton and then wrote your own code, you wouldn't have missed it.