Screwing up at work
Someone on the security team signed off that a fake bomb had been recovered at Old Trafford when it hadn't. Cue one controlled explosion and a postponed soccer game. Tell us your tales of workplace screw ups and the consequences of your mistakes.
( , Tue 17 May 2016, 8:59)
Someone on the security team signed off that a fake bomb had been recovered at Old Trafford when it hadn't. Cue one controlled explosion and a postponed soccer game. Tell us your tales of workplace screw ups and the consequences of your mistakes.
( , Tue 17 May 2016, 8:59)
« Go Back
20 years ago, I was a young computer programmer working on an antiquated IBM Mainframe
I was working on a 'leading edge' project that was trying to pass PC-based transactions to the mainframe for processing and then back again.
Whilst testing one afternoon, we discovered that one of my programs was continually failing. No big surprise in itself, but these repeated failures rapildy fill an audit log file, which in turn brought down the entire company mainframe.
The whole company, some 500 or so employees, were left twiddling their thumbs for the rest of the day. Lost productivity was probably in the order of 10s of 1000s of £.
An IBM engineer was called, who was adamant that something as bog-standard as a program failure would NEVER make an entire mainframe crash. Oh how wrong he was. He ended up taking my program away with him 'for further investigation'.
Incredibly, I didn't get so much as a mild bollocking. They were more annoyed with IBM than me.
tl;dr - Zzzzzzzz boring IT stuff.
( , Tue 17 May 2016, 14:02, 1 reply)
I was working on a 'leading edge' project that was trying to pass PC-based transactions to the mainframe for processing and then back again.
Whilst testing one afternoon, we discovered that one of my programs was continually failing. No big surprise in itself, but these repeated failures rapildy fill an audit log file, which in turn brought down the entire company mainframe.
The whole company, some 500 or so employees, were left twiddling their thumbs for the rest of the day. Lost productivity was probably in the order of 10s of 1000s of £.
An IBM engineer was called, who was adamant that something as bog-standard as a program failure would NEVER make an entire mainframe crash. Oh how wrong he was. He ended up taking my program away with him 'for further investigation'.
Incredibly, I didn't get so much as a mild bollocking. They were more annoyed with IBM than me.
tl;dr - Zzzzzzzz boring IT stuff.
( , Tue 17 May 2016, 14:02, 1 reply)
Mrs Groover..........
.....has a cousin who works on mainframe IBM computers, repairing cock-ups for the past forty years. It will be his fault, not yours. He's a complete nerd. Sleep easy.
( , Wed 18 May 2016, 20:38, closed)
.....has a cousin who works on mainframe IBM computers, repairing cock-ups for the past forty years. It will be his fault, not yours. He's a complete nerd. Sleep easy.
( , Wed 18 May 2016, 20:38, closed)
« Go Back