Yeah, sure, as an IT professional it’s a bunch of fun to complain about stupid users. But when IT folks make a mistake, it can be a whopper. You don’t even want to think about the thousands . . . no, the millions . . . of dollars you could cost your company. Or the post-disaster remedies that could include you-know-who’s job.

Trouble is, real IT damages don’t often arise from runaway arcs of electricity like in Doctor Frankenstein’s lab, but more often in plain old IT oversight or neglect. To bring the point home, here’s TechRepublic’s “Ten Dumb Things IT Pros Do That Can Mess Up Their Networks.”  (We’ve obviously abridged the list. You can get a PDF below.)

#1: Don’t have a comprehensive backup and disaster recovery plan.
Many backup strategies haven’t changed in decades. You set up a tape backup to copy certain important files at specified intervals and then forget about it. You don’t get around to assessing and updating that backup strategy–or even testing the tapes periodically to make sure your data really is getting backed up–until something forces you to do so (the tape system breaks or worse, you have a catastrophic data loss that forces you to actually use those backups).

#2: Ignore warning signs.
As with our physical health, it pays to heed early warning signs that something is wrong with the network and catch it before it becomes more serious.

#3: Never document changes.
When you make changes to the server’s configuration settings, it pays to take the time to document them. You’ll be glad you did if a physical disaster destroys the machine or the operating system fails and you have to start over from scratch.

#4: Don’t waste space on logging.
One way to save hard disk space is to forego enabling logging or set your log files to overwrite at a small file size threshold. The problem with that is that disk space is relatively cheap, but hours of pulling your hair out when you’re trying to troubleshoot a problem without logs to help you discover what happened can be costly, in terms of both money and frustration.

#5: Take your time about installing critical updates.
The “It’ll never happen to me” syndrome has been the downfall of many networks.

#6: Save time and money by putting off upgrades.
Upgrading your operating systems and mission-critical applications can be time consuming and expensive. But putting off upgrades for too long can cost you even more, especially in terms of security.

#7: Manage passwords sloppily.
Bad password policies and sloppy password management create a weak link that can allow attackers to invade your systems with little technical skill needed.

#8: Try to please all the people all of the time.
Network administration isn’t the job for someone who needs to be liked by everyone. You’ll often be setting down and enforcing rules that users don’t like.

#9: Don’t try to please any of the people any of the time.
Just as it’s important to stand your ground when the security or integrity of the network is at stake, it’s also important to listen to both management and your users, find out what they do need to do their jobs, and make it as easy for them as you can–within the parameters of your mission (a secure and reliable network).

#10: Make yourself indispensable by not training anyone else to do your job.
This is a common mistake throughout the business world, not just in IT. You think if you’re the only one who knows how the mail server is configured or where all the switches are, your job will be secure. The sad fact is: no one is indispensable.

For more detail on these ten dumb things, click here for the full article.

InfoWorld dishes up this collection of True IT Confessions — seven stories wherein “Supergeeks fess up to some of the dumbest things they’ve ever done.” Basically, these are the IT equivalent of the carpenters’ old adage, “Measure twice. Cut once.”

Any dumb things you’ve done (IT-wise) you’d like to share?