Slashdot Mirror
Getting Rid of Staff With High Access?
HikingStick writes "I've been in the tech field for over 15 years. After more than nine years with the same company, I've been asked to step in and establish an IT department for a regional manufacturing firm. I approached my company early, providing four weeks notice (including a week of pre-scheduled [and pre-approved] vacation time). I have a number of projects to complete, and had planned to document some of the obscure bits of knowledge I've gleaned over the past nine years for the benefit of my peers, so I figured that would give me plenty of time. That was on a Friday. The following Monday, word came down from above that all of my privileged access was to be removed — immediately. So, here I sit, stripped of power with weeks ahead of me. From discussions with my peers in other companies, I know that cutting off high-privilege users is common, but usually in conjunction with a severance offer (to keep their hands off the network during those final weeks, especially if there is any ill-will). Should I argue for restored access, highlight the fact that I am currently a human paperweight, request a severance package, or simply become the most prolific Slashdot poster over the next few weeks? Does your company have a policy/process for dealing with high-privilege users who give notice? What is it, and do you make exceptions?"
Completely unaware of the fact that I was about to be laid off, I had kicked of an elaborate SQL script on the live server just before my boss called me into his office. They killed my account with this script still running-- oops. A friend of mine who was still at the company said that the resulting zombie crashed the main Oracle server, requiring a reboot, three days after I left.
How very childish of you. I hope that story makes the rounds in your community and you have a hard time getting work.
Purposely thrashing a system helps no one. Being pissed that your being laid-off, that is understandable. Throwing a tantrum over it indicates the company was probably exercising good judgment in letting you go. Hell, the lay-off many have just been a convenient excuse.
Really, why go to work at all? What are they going to do, fire you? I suppose they could try to not pay you for that last four weeks, but that's just asking for a lawsuit or labor relations complaint, so they probably won't. If you feel like being a bit more conservative, go in late, leave early, and take long lunches. Or just show up each day, or even once a week, long enough for people to see you're there.
You're not really helping anyone out if you're sitting bored at your desk because you can't do your job. Not your co-workers, not the company, and not yourself. It's just a combination of stupid policies.
And this is why people wipe others asses, clean the floors and run the network for others their whole life. Losers actually ask their bosses how they can continue being a loser. Business is about screwing first and avoiding damages. The OP spent that long at the company and never expected them to revoke his privs? This just means that after all this time they never learned anything and might as well have been sanitizing the corporate toilets, but instead sanitized the network.
Way to go, Janitor. You sysadmins think you are so cool with your cables and servers. But really the culture above has never changed and all you are is a servant doing their dirty work. If you actually pushed a broom you might get some excerize.
The world is not a cooperative place and it amazes me every time when someone is surprised to find this out. So much, that I do not even consider this post to be authentic.
Nobody could be that stupid.