Wednesday, May 13, 2020

Nuclear Revenge: Supervisor Takes Credit For Man's Work, Man Ruins Operation


Moral of the story in this particular case of a nuclear revenge is to not mess with the dude who can royally mess up the machinery that you count on. This supervisor thought that they were so clever, running off with the guy's breakthrough, and pawning it off as their own. That whole line of BS, about having to put in the time to get where the supervisor was at, was real rich as well. Fortunately, the guy who had his work stolen was able to execute a calculated revenge of epic proportions. 

1.

Text - r/NuclearRevenge + Join u/Totesmgoats33 • 313d 1 3 1 supervisor takes credit for my work, I cause entire production to shut down. I started working in a machine shop after I finished school with a 2 year degree in machining. Learned all kinds of programming techniques that could make most machines that were less than 30 years old perform moves, and output measurements of parts currently in the machine to automatically perform quality control. this greatly increases quality of parts as wel

2.

Text - It's my first day on the machine shop floor, and I immediately notice inefficiencies in all the machines in my station. We had to manually perform quality control, sacrificing production time, while also leaving tons of room for human error due to the poor quality of measuring instruments in the shop. I'm new and eager to prove l'm worth more than the original pay they offered. I told my supervisor to let me spend an hour to add a line of code to a machine to demonstrate my skills I learn

3.

Text - Quick backstory to note.l had 0 experience in a production plant, and said supervisor had 30 years experience in the field. He had a very proud attitude, and genuinely worked very hard to learn what he knew. He was decent to work with, but when I asked questions about some of the basics on this machine, like how to get to the program so I could edit it, he would block my view of what he was doing, and get to the end result quickly without explaining the process. Being new and wanting to l

4.

Text - Anyway I program the function into the machine in about 2 hours, 40 minutes, and when it comes time to demonstrate the process, it catches a part that is out of tolerances according to the blueprint. I also programmed the machine to output different messages, providing instructions to whoever the operator was on ways to resolve the issue if the part couldn't be salvaged, or to automatically adjust offsets of the tool that machined the feature that was found to | be out of tolerances, and

5.

Text - This is a pretty magnificent feature to have in production, and my supervisor knew that. The supervisor who observed the demo immediately went to report this to higher ups, who came to view the new feature I had implemented. As the next part was being produced, the quality check move initiated and found that the 2nd part was also bad, and output a message to change tools x, y and z. The managers were incredibly surprised that this was all done on a 18 year old machine, and they looked to

6.

Text - The next day, I was planning on informing the managers that I was the one who did the programming to do that. The managers were also former machine shop veterans with 20+ years in the workplace and refused to believe me. Not only that, they basically yelled at me for trying to steal credit from someone who has worked their way up in the company and learned everything on their own and not from some school.

7.

Text - I went to my station even more pissed now, where I was met by my supervisor. He told me that I needed to go around to all the machines that could perform that function and add it to the code. I said" not without a raise. My code saves you guys tons and brings the bottom line to a level that McDonald's qualified workers could produce infinite numbers of parts with minimal loss."

8.

Text - He said if I didn't do it, I would be fired. So I faked my compliance and started to change code on all the machines. If you know anything about programming, you know you can make something function a certain way until a certain value is met, and then have it completely change afterwards. This was MY job security. So I set the quality check up on 18 machines the first day, then the last 30 that weekend, and the managers were praising the supervisor uncontrollably for his innovation.

9.

Text - Well, the programs were all set to operate as normal, and do quality checks like I programmed the original machine. However I programmed the rest of the machines to keep track of a new variable. They would run and self check just fine... until they reached a random number of parts produced (50-500 depending on the production time of the parts run on each machine) where it would then throw up an error code, that would only be cleared with a password I had set for it. If a wrong password wa

10.

Text - It took 3 days for the machines to hit their magic values, but when they did boy oh boy was it magically satisfying. The first machine to crash was making parts for the drivelines of a major motor company. The crash was caused while a new operator was running the machine, who I might add was only hired because the program I made let them hire clueless people into the shop and be able to still produce good parts. When He tried to clear my password code, the lathe started turning at 2500 rp

11.

Text - After the first glorious crash, I menacingly mention to the supervisor, "you should check your codes to make sure they're working properly". He went ghost white. Not a second after, 3 more machines simultaneously crash in glorious fashion. He starts to chew me out, saying I'm in huge trouble, but as he starts cursing, the managers are there to have him go diagnose the problems with"his" codes. The supervisor, not wanting to admit he stole my work, doubles down, and says confidently "I kno

12.

Text - This is a 24-hour production facility with 3 shifts of workers coming in 7 days a week mind you. Our shift is nearly over and we've all been idle for about 7 hours. The next shift comes in and we leave for the day. I hear nothing from the shop, so I just go in the next day as normal.

13.

Text - Turns out they tried to fire machines back up during the night shift and 18 more machines crashed like the others. The plant did a formal layoff of most the workers the next week, as they were hemorrhaging money from all the damaged machines on top of labor paid without any production. We filed a class action suit against the company for unemployment, lost vacation time, dangerous work conditions due to the severity of the crashes, etc. The company went bankrupt from the lawsuits and loss

14.

Text - The guy who took my credit was obviously fired, and had an article in the paper about him sabotaging the companies production. He obviously told them I was responsible for the crashes, but the company found out that the code to my password program was his name. They believed he did this out of spite cause he was refused a raise the previous year and his threats to them after his last evaluation. Sucks to suck lol.

15.

Text - EDIT: To all in the comments worried about the innocent workers, they were given 2 months severance pay on top of being able to collect unemployment for 16 weeks. The severance pay outlined by the lawsuit took into account all the benefits the employees had before getting laid off. I DO FEEL GUILTY THAT THERE WAS COLLATERAL DAMAGE. However, most the employees ended up with the equivalent of about 6 months paid vacation. So there is a happy ending :) I honestly didn't think the company wou

Submitted by:

Posted by at
Labels:

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)