Rule 4: Practice your disaster recovery plans
Develop disaster recovery plans and practice them like you might conduct a fire drill. Make sure you can smoothly slide to an alternate system or backup server as needed while you get the problematic one back in shape.
Rule 5: Automate anything you have to do more than three times, especially when it’s complicated
Scripting routine tasks, especially complex tasks, will avoid potential mistakes. It will also save you quite a bit of time and make it easy for someone else to run the script when you can’t.
Rule 6: Never rely on a script you haven’t thoroughly tested
Always test your scripts to be sure that they work exactly as you intended – especially complicated scripts.
Rule 7: Document your work
Document your scripts and your routines well enough that someone else understands what to do when you can’t. Scripts should have enough comments to make them easy to read and, if necessary, modify. Add just enough comments to make it clear what the script is doing. Over-commenting on obvious commands is counterproductive.
Rule 8: Pay attention to your mistakes
Everyone makes mistakes from time to time. Pay attention to the kind of mistakes that you tend to make – that can help you avoid them.
Rule 9: Be a little paranoid
No, don’t actually be paranoid, but don’t be overconfident either. Look for potential problems in the work you do, and ask yourself what could go wrong and how you might prepare for it.
