Biggest fuck up you ever made at work?

Just remembered one…

Someone (not me) had created some shortcuts on our system to common commands. These shortcuts were numbers, so you type ‘1’ you get one command. Type ‘2’ you get a different command and so on.

I disagreed strongly with this on the grounds that it is dangerous. As proved by the events that transpired…

One day we were rushing to get the system started. I wasn’t a Manager at the time so I was being told by the then Manager what to do. I started typing out the full command…

‘set_exchange_rate_rand_to_us’

“No. Type 46” said the Manager.

“I prefer to type the commands” says I.

“There’s no time. 46.”

So I do. I type 46. enter the amount of rand to the US dollar (7 or 8).
At the end of the day it transpires that the conversion had been done in reverse (7 or 8 dollars to the rand)

The command we wanted was ‘45’ ( ‘46’ is ‘set_exchange_us_to_rand’)

It was the Manager’s error in telling me 46 instead of 45. It was MY error to be stupid enough to go ahead and do as I was told instead of using my own common sense and standing up to the Manager “No I’m doing it my [safe] way”

The error cost the compant $30,000

Alas, I am now the manager, and the unsafe shortcuts have been deleted.

When I was a Cafeteria Slave at Grand Canyon National Park I was charged with cleaning out the ice tea bins at closing time. These were HUGE dispenser/brewers, about 4’ tall, and cleaning them was a bitch. One night I was so tired I dropped the cleaning sponge in the dispenser and forgot to fish it out.

The sponge marinated in there for a few weeks until it started to break up and come out as teeny pink bits in tourists’ drinks and the manager had to start refunding money for the mystery drink. He went ballistic when he figured out what it was, but I never got pinned for it.

My other memorable screw-up was at a special events company I worked at. I sent out a bunch of client letters and managed to type “Peninsula Bank” as “Penis Bank” in the header, with the salutation reading “Dear Ms. Penis.” This was in Ye Olde Days when databases were a nightmare to edit, so I made a new entry but made the same typo AGAIN and sent the letter out without noticing. The client called to complain that she had received two letters addressing her business as such and my boss chewed me out and told me to fix it and send it again.

Guess what happened? Yup!

In my young days as a programmer, I was charged to update our database of items for sale, reducing by 10% the price of items in category X. The next morning the new, improved price list would be sent out to a bunch of associated vendors, clients, etc.
It would have been good if my update job had included the condition “when category = X” instead of just reducing the price of EVERY ITEM by 10%.
I learned from that to always run my program on the dev system first, and check the results.

This one is not really my fault, but I’ve always enjoyed this story.

In my student days I was employed as a programmer at a state transportation department in the US. Their main system was an old mainframe, and it was so old that we wrote programs when logged in directly to the same IBM mainframe used by everyone in the transportation department. (Of course programmers had accounts with low privileges.) We used an old character-based text editor named ROSCOE.

One day, I decide to copy and paste line X from position Y to position Z in the text editor. After I paste line X, crash the whole mainframe goes down. Oh well. After an hour, they bring the system back up. I log in, and start again from the same point: bring up my program in the text editor, copy and paste line X from position Y to position Z. crash the whole mainframe goes down. This time it’s up after about 45 minutes. I tell the guy sitting next to me “I think I brought it down with my editor command”. He tells me I’m crazy, how the hell can an editor command bring down the whole mainframe? But I call the operators anyway and they say “it’s impossible for you to bring the system down by doing something in the editor.” I ask my colleague “Should I try it again”? “Do it! I’ll give you $10 if the system goes down when you do your copy and paste.” I try my copy and paste. Guess what happens?

The operators have been improving, this time it’s up after 30 minutes. I call them again and say “you know what? 3 times now I’ve done this editor command and the system went down immediately afterwards.” One of the operators tells me to come down to the computer room. They’re calling my bluff. He brings over the systems adminstrator, who is shaking his head at the impossibility of what I am saying. “Go ahead and show us what you were doing”. I log in, bring up the same file, do the came copy and paste command. Crash!

“Ok” the system administrator tells me “stop doing that.” After an hour they call me back down there. An IBM consultant is there (he’d been called after the second failure) and he says he know what the bug is and has fixed it. “Show me exactly what you did, it’ll work now” says the consultant. Here we go again. After I paste my line - two guesses as to what happened.

The next time the system came up, I was told that the bug was definitely fixed, but this time, instead of copying and pasting, I retyped in the line of code in the new location.

One of the guys at work kept going on about those sexy chat phone numbers and making jokes about calling them. I called “The Bosses Hands”, and put the call through to him. He listened for ages, I had to go down to his office (I could see the light still on the switchboard) and try to get him to hang up but he waved me away.

When the phone bill came in questions were asked and he busted me!

I won’t talk about mine, but my husband’s couriosity has caused special labels to be placed on hazardous chemicals throughout the Big Airplane Manufacturer family that say, “Keep out of the reach of children and picunursre’s husband.”*
*Names have been changed to protect the foolish.

Wow! You invaded Iraq? That’ll harsh your buzz.
I was running a small crew servicing oil field pumps (grasshoppers). These things were out in the boonies so they were diesel powered. We would check them over, fuel them up, and start or stop them per schedule. One fine morning the company geologist came by in her new company truck. As one of my guys gave her directions, I finished checking the engine and was ready to start it up again. But that makes a fair bit of smoke & noise so I waited. After a minute she said goodbye and I hit the starter. Just then a mouse ran out from behind the air cleaner and scampered across the engine block straight into the flywheel housing. Somehow it got grabbed, mangled, half skinned, and flung in a graceful arc right through the open window and into her lap. I gotta say, she took it well. Hell, I woulda shrieked at least that much.

I was driving an ancient 5 ton flatbed. I had been whining for ages that the thing had a front end shimmy like Zsa Zsa Gabor when you hit the brakes. The boss said it was on the list to get fixed and I just had to baby it along. End of a long day, I was about a mile from the shop with a load of well casing when some dipshit came bombing out of a side street directly in front of me. I mashed the brakes and with a huge thump-smash-grind the entire front axle fell out from under the truck and bounced off down the highway. Somehow I missed the dipshit and skidded to a stop shiny side up. I found a new job before the month was out.

I was working in a welding shop. One of the guys borrowed the 220 V extension cord from my machine while I was working with the torch for awhile. I got done with the cutting and needed the welder. So I plugged in the extension cord and walked around the corner to fetch the other end. That’s backwards. I found the old guy sitting about 10 feet from a barrel of water with a half torn down pump clamped to it. I lit his ass right up and it’s just random chance he wasn’t killed. I got fired and deserved it.

I think I’ve told this story before, but when my Dad was a student at Northern Arizona U in the 40’s, he was cleaning out a hot chocolate dispenser. At the bottom of the container, he noticed an object and pulled it out. It was a denture plate. An old lady who worked at the kitchen came over and said, “That’s where it was”. She took it from my father’s hand, popped it in her mouth and went back to work.

Someone we know recently crashed a $200m Boeing 777 into the runway at Heathrow.

He is no longer allowed to criticise his girlfriend when she reverses into bollards in the car park.

As plant engineer I had taken over some maintenance related tasks that the operators should have done, because they were on break and I wanted to get it done and go home.

I unlocked, but neglected to open, a 1/2" valve whose job it was to control the flow of about 6 oz of magical fluid into a 3000 gallon batch reactor. The magical fluid was antifoam (fancy soap) without which the batches in a dozen reactors frothed madly up into all the head piping and froze solid.

Shut the plant down for ~24 hours, kept about 18 people out of bed for that time. Almost caused short shipping to several auto parts suppliers who have fines in their sales agreements to the tune of $50,000 per hour.

I had the Putz Trophy on my desk for a couple of years after that.

not_alice: great story; was the astronaut disciplined for the ad lib? You’d think forgetting the rules of mass in space might warrant a slap on the wrist (but not while he was in space - the slap would start him tumbling, right?)

and **pullin **- you rolled a UPS Truck? Do tell.

I got nuthin’ - I mean, don’t get me wrong: I screw up constantly, just nothing this…epic. I am more of an incremental screw-up :wink:

I did almost the exact same thing, using vi on an IBM AIX system. I locked up the student information system for a major university. Twice.

Nice going WVmom. I should have bought myself a T-shirt that said “Fear the Programmer”. You can get one too.

I would be wildly amused if I found I’d bought a package of sausage that old!

Did anyone notice? :smiley:

I once accidentally sent four semi-truck loads of scrap plastic from central Indiana to Louisiana, instead of across town, as was intended. Oops. The company had to pay for it, both to get it there, and then back home, where it was supposed to be. I got chewed out, but I didn’t get fired. I left shortly after, because I obviously sucked at that job.

Did I mention that I am impressed?

[/violent femmes]

They fired you for saving some idiot’s life? If you had plowed through him and saved the truck would you have gotten to keep your job?

Someone helped me remember the actual mission via PM. Credit where credit was due, but since the P is for private, unless he pipes up and approves me telling, he (she?) will have to live with this credit :slight_smile:

Anyway, here are some links.

http://heasarc.gsfc.nasa.gov/docs/he.../solarmax.html

STS-41-C - Wikipedia (which confirms my story about the astronaut grabbing it by hand)

I never knew there was an IMAX movie!!!

The Dream Is Alive - Wikipedia

And it occurs to me there was more then a little scuttlebutt and concern around the office that the astronaut himself could have had his suit punctured and/or been sent into a hopeless tumble as well. Luckily that didn’t happen.

I see from the articles here that the particular Shuttle had an untimely ending later, I had never made that connection either.

And although by this time I had left NASA, I wrangled a nice view of the live feed of the Hubble Launch (I worked a long time on that project). I remember deja vu when the satellite was released and one of the solar panels only partially deployed. I wondered if an astronaut had to go pull it loose what would happen. Luckily that one was solved from the ground too and we all know how that mission turned out.

Epic Fail

Wasn’t me. Honest. No, really!

They didn’t fire me, I quit. When I got back to the office I was red hot about almost getting killed by the company’s crappy old equipment. Remember, I was sitting in front of 5 tons of pipe. I expected a few attaboys or maybe even an apology. Instead the boss ignored me while he ranted about the cops and the cost. That was the last straw. So I kept my trap shut for two weeks while I found a job where management actually spent money on maintenance.

A couple from the same factory, neither was mine:

The usual “entry level spot” was as a production peon (actual job title, ok?) in the weekend shift, but they’d spend the first four weeks working the day shift as on-the-job training.

One day, I went to have lunch and the latest arrival was looking terribly sad, like a kicked puppy… he was feeling so bad he couldn’t even eat (and on a 21yo man, that’s a lot of “feeling bad!”). Turns out that, while trying to place one of the m[sup]3[/sup] containers (called “cages” because of the metal cage around the actual plastic container) “just so,” he’d pierced the one behind with the cart’s “horns”. The other guys laughed and explained to him that actually they figured it meant he’d stay. They said, “you did it for trying to do better than the cart and cage specs allow, not for going too fast or somesuch. Most of us horned a cage during our trial period :D” A quick poll proved that the only two people in that room who’d never “horned a cage” where the only two who had never pulled a warehouse shift.

One fine, cold Saturday, I get to work at 6am and the lab tech from the previous shift tells me to change into a borrowed blue overall instead of my lab coat.

Turns out that one of the night batches wouldn’t start reacting; after running through the first steps of the standard protocol, it was time to call the Emergency Duty Person… but seeing who it was (let’s call him Bob), the foreman said “oh no way, screw it, I’m winging this myself and if I do it wrong let them fire my ass.” It looked to him like heating more or adding more reagent would be likely to cause an explosion or at least an explosive polimerization, which would in turn be dangerous for life and limb or at the very least involve long and dangerous cleaning. So he dumped the load instead, by opening the trapdoor at the bottom of the reactor. Part of the load reacted when it touched the cold floor, part went into the drains (the factory had its own sewage purification system) and stayed liquid.

We spent the whole weekend and part of Monday morning cleaning up the white, spongy, sticky cake off the floor but it was nothing compared with what any of us knew could have been. And it was during the slow part of the year, so there was no impact to customers.

The manager started to berate the foreman for not calling the emergency guy (as well as congratulating him for solving the situation correctly), but when he said “it was Bob who was on duty,” she couldn’t find the courage to go on.

About ten days later, a different factory had the same situation… only, there, they pulled what we called “a Bhopal:” they kept bouncing the decision up, add more reagent, heat up more, bounce it up… until they got an explosive reaction which didn’t cause personal harm but required over two weeks of cleanup. Everybody above the foreman (foremen weren’t supposed to take the “dump it” decision, but those above could) got fired.

Why Bob got no respect:
I’d worked in that factory for over a year and wondered why Bob got no respect. After all, he was an engineer, most “bluemen” would respect anybody with any kind of tech education, so why not Bob?

One of my duties was to prepare small batches to test new recipes. Bob had tweaked a recipe and told me to test it for him. I ran the recipe as written but the reaction wouldn’t start. I followed the usual protocol until the point where if it had been a weekend I would have had to scrap it and start a fresh one, but it wasn’t the weekend: it was a weekday and Bob was there, so I went to inform him. He said “oh, add more starter reagent!” “I already did, twice per protocol, and it’s not starting. Protocol calls for scrapping.” “Nah, can’t be, let’s go take a look at it.” (Btw: he was a mechanical engineer, I was lower on the factory’s totem pole but I’m a chemical engineer, so when it comes to organic reactions I’d like to think I know a bit more than he did)

So we go, and the foreman on duty (different foreman, Joe) was there, having brought a sample from the Big Reactor for me to analyze.

Bob told Joe to wait. This was a serious breach of protocol: running a sample from the Big Reactor was higher priority than anything other than fire, broken bones, heart attacks and bleeding wounds. But Bob was higher in the totem pole than we were, so Joe waited while Bob poked at my minireactor and… poured all the starter in :smack: Can you spell “volcano”? Well, the eruption was white, but you know what I mean.

And while I stopped the explosive reaction he had caused, Bob freaked out so badly that Joe had to grab him out of my way and was seriously considering bitchlapping him from the factory to Bangkok by the time Bob collapsed into a chair crying “ohmygod, ohmygod, what can we do?” “What she’s already doing… :rolleyes:”

Joe and me cleaned things up, including Bob’s shaking nerves. But I understood that day why he wasn’t someone you’d want to call when you had a problem, indeed.

I was driving the company car, and got it stuck in a centuries-old stone gate. It was a very narrow gate, but many people drove cars through it every day, and I myself had done it successfully in the past. This time I must have come at it a little off, and that car was solidly wedged in there. Like a sofa in a stairwell, it wouldn’t go forward and it wouldn’t go back, either.

Enough of the car was hanging out into the street to prevent traffic from moving. On a major street. During evening rush hour.

One nice guy got out of his car (well, it wasn’t like he could go anywhere anyway) and helped push to get my car unstuck. It finally came free, crumpled up like a little tin can. I think the gate was mostly undamaged.

My boss was really nice about it, which made me feel worse.