Brainfarts at work and other gobsmacking stories

HunterNW said:
Also ages ago:

Qualified for just over a year and had to stand in on the winder. (The lift that takes you underground)
Some problem on the braking system and i suspected an 0-ring popped and got stuck in the one hydraulic valve.
Switched off the hydraulic pumps, locked out and started loosening the valve hex screws. Fokol. This valve was sticking to the manifold like a vjayjay to a tile floor.

So I yanked on it and BOOM ! In a split second i'm soaked in hydraulic oil. Even the electrical foreman who stood a couple of meters away had oil on him. (After fixing the valve who had an o-ring stuck in a port i went to the change house to put on another overall, my underpants were so soaked with oil I through it away)

The problem: Even after stopping the pumps, there's an accumulator still filled with oil under pressure. 10MPa.
(Stored energy). Things could have gone seriously south.
Click to expand...
Oh reminds me

Last year, during the year end function I arranged for a hydraulic pressure sensor to be nicked from one of the dozers in the yard, needles to say, I forgot about it. So in the new year guess what happened when they started the dozer, sprayed one of the bakkies moertoe, through the side of the workshop, like a 10 meter stream:ROFL:
 
Worked for a well known television company. Employee used a XML file to determine which countries are able to use their pay to view movie service. Anyway, employee was under the impression they were the only one working with this file, so they didn't bother getting an updated version from the server just continued using the one they had on their local. Anyway, that's how boxoffice was killed for Botswana for a day or so.

edit: It totally wasn't me.
 
Dropped a model-master table at a major vehicle manufacturer, bringing a halt to vehicle and part orders across the country. Just for 30 minutes. DBAs were more concerned that there were no logs at all as I used a tool from the database vendor they were not aware of to sync databases.

At least that was better than the DBA at major insurer who wanted to create a log of all faults on the environment and added code to log all errors across the whole integrated estate. Issue was that it was accepted practice for developers to allow the error routine to do backout transactions. The dba, who knew this, added code and commit before the backout, creating havoc with three days of incomplete transactions. Business had to roll back three days. That dba was not popular, especially as he always nailed people with processes and peocedures. Of course he did not follow any of that
 
Locked myself out my bitwarden account , and didnt write down my recovery code :X3:

Lucky its just a test environment :)
 
I bet the worst department to work in is the IT department especially in a large company, the amount of things that could go wrong is crazy!
 
At a well known data centre, one techie could not get out while in the data centre.
He decided to press the fire alarm so that the doors open.
When pressing the fire alarm, Sodium bicarbonate and mono-ammonium phosphate gets released and that stuff goes into any server!
 
karnuffel said:
Worst Ive done was to, in a moment of what can only be described as insanity, disable the network adapter of a server as was remotely logged onto. Had to get someone at the datacenter to walk over to the machine and enable it again.
Click to expand...
I managed effectively this while configuring a VPN on our server at a datacenter remotely, something not really in my skillset but you do what needs to be done in a small company.
I remember clicking "apply" and the RDP session immediately disconnecting. I had to drive to the data centre first thing in the morning when they were able to provide access to the server, to go fix my **** up.
 
My self-pwnage story.

I have a supplier who sends a stock feed as XML with stock levels displayed the following way:

A = 0
B = 1 - 19
C = 20+

I do a replace all on that column to A=0, B=3, C=15 before saving and uploading as a CSV. Anyway, one day I noticed feeds weren't updating successfully so I had a look at the CSV and noticed that StockLevel is now called Sto15kLevel. Mkay, edit my update script and it works for a few days, then breaks again. The column is once again called StockLevel.

I'm losing my ****. I cannot work with these frequent, nonsensical updates to the column headings. I call the supplier. I speak to technical. I'm beyond annoyed because they can't comprehend what I'm explaining. I'm trying not to shout. I'm really holding back. I... realize that on some days I'm accidentally selecting the top cell of the column and renaming it myself with the replace all. I hang up without another word.
 
Progenix Oj101 said:
My self-pwnage story.

I have a supplier who sends a stock feed as XML with stock levels displayed the following way:

A = 0
B = 1 - 19
C = 20+

I do a replace all on that column to A=0, B=3, C=15 before saving and uploading as a CSV. Anyway, one day I noticed feeds weren't updating successfully so I had a look at the CSV and noticed that StockLevel is now called Sto15kLevel. Mkay, edit my update script and it works for a few days, then breaks again. The column is once again called StockLevel.

I'm losing my ****. I cannot work with these frequent, nonsensical updates to the column headings. I call the supplier. I speak to technical. I'm beyond annoyed because they can't comprehend what I'm explaining. I'm trying not to shout. I'm really holding back. I... realize that on some days I'm accidentally selecting the top cell of the column and renaming it myself with the replace all. I hang up without another word.
Click to expand...
And that is why we automate **** :D
 
Progenix Oj101 said:
My self-pwnage story.

I have a supplier who sends a stock feed as XML with stock levels displayed the following way:

A = 0
B = 1 - 19
C = 20+

I do a replace all on that column to A=0, B=3, C=15 before saving and uploading as a CSV. Anyway, one day I noticed feeds weren't updating successfully so I had a look at the CSV and noticed that StockLevel is now called Sto15kLevel. Mkay, edit my update script and it works for a few days, then breaks again. The column is once again called StockLevel.

I'm losing my ****. I cannot work with these frequent, nonsensical updates to the column headings. I call the supplier. I speak to technical. I'm beyond annoyed because they can't comprehend what I'm explaining. I'm trying not to shout. I'm really holding back. I... realize that on some days I'm accidentally selecting the top cell of the column and renaming it myself with the replace all. I hang up without another word.
Click to expand...
Hopefully you apologised.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X