New Boss Immediately Began Forcing Changes And Fired A Key Developer, So He Ends Up Taking Their Entire System Down Because He Was The Only One Who Could Fix It
by Michael Levanduski
When a new boss comes in, they can either do the right thing and make no changes while learning the systems, or try to overhaul things on day one.
What would you do if your new boss required you to make changes that you knew would cause problems, and then fired you for it, which resulted in their systems quickly going down?
That is what happened to the developer in this story, and he refused to come back to work, which caused his boss to get fired.
Check it out.
New boss mobs and then fires admin. Major systems go downhill and boss is in hot water.
So, i worked for this multinational company for over a decade as a system administrator.
My responsibility was in the area of manufacturing, mostly for central systems that work on data flow between the manufacturing systems and the ERP system in near-real-time.
Even though the company had lots of cash for stupid projects, IT budget was always too tight for those expensive, customized data munching systems.
So, shortly after starting to work at the company, I started implementing my own.
(I’m also an experienced software developer, one of the reason my original boss hired me)
I won’t go into too much detail, but i decided to make the stuff web based for easier deployment of updates.
It worked great, and over time more and more functions got ported into this easy to enhance/easy to update system.
These types of systems work using duct tape and prayer.
Partly new stuff, partly decades-old software that was in dire need of replacement.
After about a decade, this system was rather central to the manufacturing process in many ways, and yes, there were hot-standby servers, multiple backups each day and so on.
Due to the severe budget constraints, I’m allowed to use open source software for my database.
I’m also allowed to use my own open source web system as the base for it all and keep it open source (except for some small, selected parts that are company specific).
I’m pleased about that, because, essentially, the company is paying me to progress my open source project while getting a friendly, reliable system for me to use at work.
I always had the support of my varying bosses over the years (we change middle management a lot).
In comes another new boss.
In the first ever talk we have, he complains that the software is written in [programming language] because that’s “so outdated”.
I tell him it’s actively developed and used by a number of Fortune500 companies for their backend and/or frontend systems.
He’s not happy.
He also asks me how i do all the paperwork for the project and how my former bosses managed the project.
I tell him i do everything by mail (so everything is archived on the archive mail server as per law) and my former bosses didn’t do any management because the users and department leaders are happy about how i manage the project myself.
Of course, because a brand new boss always knows everything.
He is livid.
A few weeks later, my boss accuses me the work as a “separate company within our company” and it has to stop, and it doesn’t matter if the whole company approves of my work and speaks highly of me.
I have to do much more (completely useless) paperwork, get approval for every small change or bugfix from two people and is generally a dick when it comes to my work.
He also loudly complains that I work alone on my projects and that I try to ruin the company by doing so.
I have it on file that I asked whoever was my boss at that time for TEN years EVERY month to have someone as backup and got DENIED every time.
You have to understand, i have Asperger’s and I’m generally not good with dealing with this stuff.
But so far, I always managed.
This day is the first ever I left early, crying my eyes out in nearly 25 years of work.
More bullying follows, and over the next year my boss starts taking away all of my duties, one at a time.
This results in me not always making my 40+ work hours per week.
You can only read reddit so much per day before you start going insane.
Now, after everything is over, I realize that was his main tactic after all, get me fired for not working as long as my coworkers.
But it just didn’t click with me at the time, because nothing like that had ever happened to me.
Boss forces me to train up “Backup” near the end February.
I only get one day to train him.
It takes a long time to get a new developer up to speed.
He’s very young and inexperienced and I complain to by boss that there’s over a decade of software development, knowledge about company rules and processes.
He also doesn’t know the programming language.
The NEXT day, after having to attend to an expensive one hours training course (and then having lunch), HR calls me in and tells me it is my last day of work.
I don’t have the usual 90 day period, but it’s my last day of being employed.
This is rather unusual in my country and only legal if both parties agree.
I agree, though, since I get a nice severance package and unemployment benefits starting the next day.
I don’t mention to HR that I was planning to quit the next month anyway because of the constant bullying.
I have one hour to clean out my desk and say goodbye to my coworkers.
The last thing i do is to have one my “backup” delete my accounts (as per company policy) while I watch.
This includes my admin account in my web system, then I leave.
I go home, cut all company access to my privately owned public source code management temporarily.
Then I work through the weekend to basically fork my own project under a new name, renaming all the classes and stuff, and release it back on my SCM under the new name.
Just so that company will have a hard time implementing all the bug fixes and security updates I do in the future.
What I accidentally-on-purpose forget to mention in the heat of the moment is that all the system documentation for the web system is also stored on the system.
And is linked to the user account of whoever wrote it (me for everything, in this case).
“ON DELETE RESTRICT” is active, so deleting a user account with active documentation is now allowed.
It works, while breaking the system.
But there is also a known safety in the software that prevents deleting admin accounts through the interface, so my coworker happily types the required command into the database shell directly.
You know, “delete from users where username = ‘the_asperger_admin’ cascade”, and it works.
Normal procedure would have the person doing the work assign a different user to that stuff first, but what the heck, I was fired and it was the responsibility of the person doing the work, not mine.
This was well documented in the documentation he has just deleted as well as in an email I sent out a couple of months earlier.
A week goes past and then the messages starts flooding in (we used a well known messaging app for real time communication and also started using it for private messaging as well, since my group are still good friends).
Parts of the system aren’t doing their job and parts of the manufacturing process has ground to a halt in multiple production plants.
The documentation is nowhere to be found and they can’t figure out what is wrong.
From what I gather, after I left they realized that I had a second account on the system, marked “Developer account, don’t change without talking to the_asperger_admin first!!!”.
Backup deleted it “since I wasn’t working at the company anymore”.
This also deleted a number of rather critical maintenance tasks running under that developer/system account and the system went belly up.
Of course, meetings are the best use of time during an emergency.
Chaos ensued, emergency meetings were held. (The company always held meetings instead of working to fix the problem whenever something went wrong).
That is when they started contacting me.
Backup: “You need to come in and fix the problem right away. Company central is already on the phone AND THEY ARE GOING CRAZY!” (adds lots of details on the problem and also on what is happening in the company)
Me: “Sorry bro, I don’t work for the company anymore.”
Backup: “But it’s your system!”
Me: “*WAS* my system. Past tense. I got fired last week, remember? I. DO. NOT. WORK. THERE. ANYMORE.”
Backup: “But we are in trouble!”
Me: “First, since I don’t work there anymore, you just violated company policy by telling me all that stuff. Could get you fired for that – but I’m not going to, you’re the SOMEWHAT innocent bystander in this.”
Me: “Secondly, on the day i was fired, HR told be that they wanted to get me out the door right away because a disgruntled worker with my kind of system knowledge is a security nightmare.”
Backup: “But you aren’t disgruntled, are you.”
Me: (playing it safe) “No. But there is no way for you or management to be sure. Are YOU willing to take FULL responsibility if you let me in and I ‘hack your systems’?”
Backup: “Uh… no… boss isn’t paying me THAT well, you see…”
Me: “And third, If I help you in any way, shape or form, I might be in deep trouble”
Backup: “What….?????”
Me: “See, the company can’t do a lawsuit against their own employees if something goes wrong by accident.
Suppliers have similar statements in their contracts and are also insured.
I’m neither of those and if I do something wrong (or the company just states i did even if i didn’t), I’m suddenly in deep financial trouble. I just can’t take the risk.”
Backup: “What if we hire you as an external supplier/contractor”.
Me: “I’d have to open a company, get insurance, go through negotiation with YOUR purchasing department to get my company in your suppliers list, then I’d have to write you an offer which you then have to get signed by [names of four people].
Which would take, all in all, 2-4 MONTHS. After which I will have to wait for the money for ANOTHER 3-4 months. Sorry, I decline”.
Backup: “Please help. Me and my boss [same person as my now former boss] are in very hot water. What can we do?”
Me: “Sorry, i can’t help the company, because it would be a risk to me. And it would be against your own company policy to ALLOW me to help.”
Backup: “Pretty please?”
I can’t imagine he will actually do this.
Me: “Tell you what. Call up company central yourself – don’t go through boss – and tell them exactly what had happened.
Tell them you broke the system by deleting those user accounts on your bosses order.
And tell them you didn’t know what would happen, because you didn’t have enough training and experience – you just relied on your bosses orders.”
Turns out, Backup actually did phone up company central a few days later.
Boss went through hell, got fired and got himself on the “never hire again anywhere in this company” blacklist for ANOTHER expensive stunt he pulled, which the company realized shortly after he was kicked out.
How do I know?
I still have lots of friends at that company and hear stuff through the grapevine.
Backup still has his job, and a new, even more incompetent boss.
So Backup is ready to find a new job.
Yesterday, he asked me about planning his company exit. Which reminded be that I wanted to write this post… and here we are.
It is crazy how many problems a bad boss can cause.
Let’s read the comments to see what other people think about the story.
Now this is good advice.
Some new bosses think they need to make big changes.
Sadly, this is a very common occurrence.
Middle management cause so many problems.
Yup, IT are the people who keep things running.
Just treat your IT staff well.
If you liked that post, check out this post about a woman who tracked down a contractor who tried to vanish without a trace.
Categories: STORIES
Tags: · broken systems, deleted accounts, fired, IT, job loss, permissions, picture, pro revenge, programming, reddit, top

Sign up to get our BEST stories of the week straight to your inbox.