 |
||
 |
 |
 |
 |
 |
|
| Let's see if I get fired in the near future by Rafiki 11/18/2015, 9:47am PST | ||||
 |
 |
|||
| I crashed a production line while troubleshooting a problem remotely. They had to scrap production and had an hour of lost time troubleshooting what went wrong. I didn't tell anyone it was my fault because I didn't realize there was a problem. At the time I thought maybe I had caused a problem, but I got no error feedback from what I was working on, the stuff I was troubleshooting was working OK, and nobody angrily called me or e-mailed me so I thought things were fine. Today I get an e-mail asking if I was dicking with the equipment because at the time I was sending out e-mails saying, "I think everything's fixed!," things were decidedly not fixed and completely broken. Whoops!
Now I'm waiting around for my boss to get back to his office so I can tell him why this business can't have nice things. If I get shitcanned, how should I go out? Half Baked style? Guns blazing? Denying everything and blaming someone else/society? |
||||
 |
 |
|||
|
Let's see if I get fired in the near future by 11/18/2015, 9:47am PST  Identify as female and claim alternative gender assignment discrimination NT by 11/18/2015, 11:34am PST Even robots fuck up production by 11/18/2015, 1:38pm PST Chinese cyber warfare did it. Lucky you were there NT by 11/18/2015, 1:48pm PST Alternately: the Mossad using a Stuxnet variant NT by 11/18/2015, 3:16pm PST Blame the process. by 11/19/2015, 12:06am PST Don't go bringing an actual answer into this NT by 11/19/2015, 12:27am PST |
