So do you think he just stood there and went opps?

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

After he unplugged half of the sunshine state?

http://www.cnn.com/2008/US/02/29/florida.outage/index.html

 

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

(Heeheehee!)

 

Ummm... oops!

Guess his employers should have looked for someone with experience, huh? ;) heeheehee!

 

Hahahaha, oh-too relevant for this forum!

 

Sounds like someone hasn't got a job anymore.

 

Maybe the employee now knows the importance of change control procedures

 

Unfortunately, he HAS!

Suspended WITH pay? He got off AMAZINGLY light!

 

Almost like winning lotto.

Actually, I think he might have said WTF?

 

I wonder what'll happen when he goes to work tommorow though.

 

Actually I am glad to see they are investigating it and not just laying it on some poor fall guy, and if they sent someone out there that wasn't qualified then that is their fault not his.

 

"Suspended" means he's not going back to work until they've finished their investigations.

 

oh seriously, damn media sensationalism!
he made a mistake
big deal

surgeons make mistakes too
but unless they have been unethical the chances are they wont lose there license, because humans are not perfect


I imagine he WILL be sacked if it turns out he deliberatly did something knowlingly wrong, it could however turn out that he knew no better though, and in that instance, I'm pretty sure his team of managers are more to blame than him

We had a load of hoo har recently when some junior civil servant lost some rather important CDs.. damn people wanted to lynch the poor guy, oh well he made a mistake, dont we all!

I think going just by what the media say in these matters is a pretty big mistake, the media are renowned for changing there tune as soon as they get all the facts

 

mmm... not of that magnitude.

 

You just haven't had the opportunity yet. Your time will come.

 

No, but perhaps the problem should be 'why does a break fix engineer have the capability to cause that much trouble?

even if corporate policy says he shouldnt anyway, how did he end up able to do what he did, without safeguards kicking in, without alarm bells going off somewhere to someone

 

You are quite correct....

...but that doesn't stop the employee from being targeted.

 

At age 38, I've had plenty of opportunities... in the military, in chemistry, and in IT. But that didn't happen because I followed procedures... and if I didn't have the procedures, I didn't do anything that MIGHT cause something bad to happen. I'm not a "What's this button do? <click>" sort of person... if I don't know what something does, I don't mess with it until I figure it out what it does first.

It's the same in IT. For example, I've never applied a critical patch to production Exchange servers in the middle of the day because I don't want to risk my users losing connectivity to them.

The last "oops" moment I had was when I downed all of the servers for a small bank. Fortunately for me, it wasn't my fault... it was due to a faulty server UPS that was failing periodically. I got into the UPS software and ran a self-test diagnostic.

You know that spinning-down sound that a server makes when it is powered off? Imagine that sound, magnified several-fold.

This was during the middle of the day. I was incredibly apologetic. But the bank president said that it was no big deal... that's why I was out there diagnosing the problem in the first place. Whew!

The difference between what I did and what the guy in Florida did was I wasn't doing something that I wasn't supposed to be doing, like disabling safeguards. Apparently, this guy disabled TWO of them. Something similar might have been if I had unplugged the UPS connected to the servers, THEN decided to turn off the UPS to stop the beeping.... that would have just been against common sense!