July 13, 2009

True IT confessions

Supergeeks fess up to some of the dumbest things they've ever done -- and the lessons they learned as a result

It's one of the unwritten laws of physics: At some time or another, everybody screws up.

But when IT pros make mistakes, they don't mess around. Entire buildings go dark. Web sites disappear. Companies grind to a halt. Because if you're going to mess up, you might as well make it count.

"I always tell my guys, hey, you're gonna do stupid stuff," says Rich Casselberry, director of IT operations at Enterasys, a networking systems vendor. "It's OK to do something stupid if you have the wrong information. But if you do something stupid because you're stupid, that's a problem. The trick is to not flip out, which only makes it worse, or try to hide it. You need to figure out how to keep it from happening again."

[ For more adventures in IT mishaps, check out Stupid user tricks 3: IT admin follies and Stupid QA tricks: Colossal testing oversights ]

We've gathered up some of the more egregious examples from IT pros brave enough to share their screwups with us. Backups gone bad, people with admin privileges who probably shouldn't, what can go south when you unplug the wrong equipment -- in some cases, we've obscured their identities to spare them embarrassment; other geeks, however, are perfectly willing to own up to their youthful mistakes.

Sure, some of these mishaps are amusing in retrospect. But don't laugh too hard. We know you've probably done worse.

True IT confession No. 1: The case of the mysterious invisible backup
Our first tale of misadventure involves a longtime IT pro who doesn't want his real name used, so we'll just call him Hard Luck Harry.

Harry had his share of mishaps when he started out a decade ago at a major networking equipment maker in the Northeast. There was the time he changed an environmental variable that broke everything on his company's financial apps, earning an e-mail from his boss ordering him to "never hack on this system again." Or the time he crashed the company's core ERP system by overwriting /dev/tty. Harry says after he accidentally ripped the company's T1 lines out of the wall with his pager, he was banned from ever reentering the telecom closet.

But the worst one happened after Harry installed an Emerald tape backup system. Did he bother to read the manual? Please. This was child's play. Just load install.exe and let the software do its thing.

It seemed to work perfectly. Four hours later, the first backup completed and everything looked fine.

Fast-forward six months. Harry gets a call late one night at home from one of his work pals. That night's backup tape is completely blank, the friend tells him. Worse, the last four weeks of backups are also blank.

As Harry soon discovered, that particular backup program installs in demo mode by default. Demo mode looked exactly like real mode and even took the same amount of time as an actual backup, but nothing ever got written to tape -- a fact that was noted in the manual, which Harry might have seen had he read it.

Read more about adventures in IT in InfoWorld's Adventures in IT Channel.

Close

On Twitter now

Misadventures

Powered by Twitter

On Twitter now

additional resources
White Paper - How to Improve Delivery of Advanced Web Applications

White Paper

Virtual Workforce: The Key to Expanding The Business While Cutting Costs

Get the independent advice and expertise you need to support a virtual workforce.

Go inside:
The three-step approach to making a virtual workforce a reality.
The four flavors of client virtualization technologies.
The three key initiatives that solve IT challenges.
Download now »
White Paper: Successfully Secure Your Wireless LAN With Wi-Fi firewalls.

White Paper

Addressing Linux Threats Leveraging Fewer Resources

The increase in Linux popularity has increased the frequency and sophistication of malware attacks. Read this 2 page white paper now to learn how you can protect your Linux environment with real-time protection that is certified by all major Linux vendors.

Download now »
White Paper - The 2009 Handbook of Application Delivery

White Paper

The 2009 Handbook of Application Delivery

Ensuring acceptable application delivery will become even more difficult over the next few years. As a result, IT organizations need to ensure that the approach that they take to resolving the current application delivery challenges can scale to support the emerging challenges. This handbook elaborates on the key tasks associated with planning, optimization, management and control and provides decision criteria to help IT organizations choose appropriate solutions.

Download now »
White Paper - Is Your Backup System Outdated?

White Paper

Mid-range Storage Considerations

A common misconception is that mid-range storage requirements are dramatically different than that of a larger enterprise. Mid-range storage users may require less capacity, but they have similar functionality and management requirements. This ESG paper examines mid-range storage needs and reviews a new solution that adjusts size while retaining value, performance and functionality.

Download now »
tomaddox 13-Jul-09 10:16am
I'm waiting for the flood of angry comments from people who have clearly never made any mistakes in their own lives or jobs demanding to know why these people were not fired and how they have the gall to continue working in IT. Come on, guys: put down the bags of Doritos, fire up those keyboards, and don't disappoint me.
Regaug 14-Jul-09 10:54am
The IT business is infamous for very long hours; a practice sometimes mandated, and always encouraged, by IT managers who are ignorant enough to think that long hours automatically equals productivity. In my 25+ years in this biz, I've known several colleagues who fell asleep at the wheel driving home after a marathon installation or troubleshooting session: two ended up in the hospital, and one of them died. In that same time, I've seen hundreds of dedicated, competent, highly-trained engineers completely screw things up, often damaging their company's bottom line, only because they were too tired and should have gone home to their lonely families hours ago. I have heard of more enlightened IT shops who setup their engineers on shifts, and actually required a person to get some rest after a certain number of hours. This also has the added benefit of forcing the spread of knowledge and expertise as one shift hands off a tough problem to the next one. You don't end up with just one guy who knows how to fix a given issue.

Sign up to receive InfoWorld Resource Alerts

Subscribe to the Today's Headlines: First Look Newsletter

Find out what will be news for the day, with our first-thing-in-the-morning briefing.

©1994-2010 Infoworld, Inc.