Being Forced to Say Goodbye
-
Hoard a copy of your work. Even if your new overlords are gutting and replacing it, ot might be useful elsewhere one day.
Source: Similar situation once upon a time. I am currently using on a daily basis what was once replaced in a different company.
Already backed up securely and anonymously
-
I tried to push back, but they are a much larger company and they made it clear that I would be playing by their rules, not mine.
I was thinking of quitting immediately, but at least in my region of the country, the IT market is really rough right now, so I can't afford to be out of work for months.
I won't last long here though. They are half owned by a private equity firm, so they run everything based on the bottom line. Their IT team is understaffed, underpaid, and they are always looking for excuses to lay folks off or fire them. Their turnover rate is pretty high, burnout is rife.
Start job hunting now. By the sound of it they are one of those PE firms that zombie walk every acquisition into mediocrity.
-
Please be careful when copying anything that could be considered your employer's intellectual property off of that employer's systems. And definitely be even more careful about using one employer's IP for a new employer (neither company would be pleased to discover this).
I am careful, but not concerned. The new company's IT doesn't give a damn about anything that I set up or implemented. Their reactions when I was describing my work and job role before the buyout was essentially, "Aww, the cute little sysadmin was making scripts and using Linux, isn't that sweet."
As far as they're concerned, all the old hardware and software are e-waste and are being scrapped. They are ripping out everything, literally. From our phone system, to our physical devices, to our firewalls, network switches, Active Directory, and file server.
They are replacing every single part of our infrastructure. Everything I built is useless in their eyes.
-
I always feel like the features I’ve worked on become my coworkers or like pets. When a specific feature breaks often, I’ll think “damnit Frank! One of these days I’m going to patch that edge case once and for all!”
Then I patch Frank and he quiets down so I can focus on the next thing leadership wants.
You get to know these things and you put care into designing them (if you didn’t put care into them, you’d likely be a hack of an IT person). It’s always hard to see them go.
Sorry for your loss.
Thank you 🫶
-
Better start looking for a new job. That company might not be in business for too long, judging from the choices that they're making. Especially, if they work in the IT space.
For sure, already reaching out to recruiters and applying to some job postings.
-
My company's buyout has been completed, and their IT team is in the final stages of gutting our old systems and moving us on to all their infra.
Sadly, this means all my Linux and FOSS implementations I've worked on for the last year are getting shutdown and ripped out this week. (They're all 100% Microsoft and proprietary junk at the new company)
I know it's dumb to feel sad about computers and software getting shutdown, but it feels sucky to see all my hours of hard work getting trashed without a second thought.
That's the nature of a corpo takeover though. Just wanted to let off some steam to some folks here who I know would understand.
FOSS forever!
Shutdown: noun
Shut down: verb
You can't straddle the lane.
-
My company's buyout has been completed, and their IT team is in the final stages of gutting our old systems and moving us on to all their infra.
Sadly, this means all my Linux and FOSS implementations I've worked on for the last year are getting shutdown and ripped out this week. (They're all 100% Microsoft and proprietary junk at the new company)
I know it's dumb to feel sad about computers and software getting shutdown, but it feels sucky to see all my hours of hard work getting trashed without a second thought.
That's the nature of a corpo takeover though. Just wanted to let off some steam to some folks here who I know would understand.
FOSS forever!
I don't think feeling sad in this situation is dumb at all
I'm with you in your pain Linux brother/sister... I'll drink a pint in your name tonight
-
I think I'm a cloud engineer, so I can't use the same reasoning as you; but when I started at my company, I was given the option of either a Linux laptop with root or a Mac laptop. Obviously I selected Linux, but about a year later they started retiring all Linux laptops. The reason for this, I was told, is because the IT department didn't know how to manage Linux laptops but they were familiar with Jamf. They did let us keep root on them, though.
I still miss using that laptop for work. The good news is, since they never implemented mandatory RTO policies, the company moved to a much smaller office. In doing so, they needed to reduce inventory, so they gave away the old laptops (sans drives) to their employees. I now own the same laptop (or a very similar one)!
In doing so, they needed to reduce inventory, so they gave away the old laptops (sans drives) to their employees. I now own the same laptop (or a very similar one)!
Yeah, IT fleet upgrades are a great way to snag some decent hardware for dirt cheap. My Plex server is running on an old HP EliteDesk that came from a cubicle. The hardware itself is often practically new, because corporate drones rarely do anything intensive enough to actually push the hardware. Just give it a quick spray with some canned air, and pop a new drive in.
-
that's actually really sad, IT of all people don't care about FOSS?
Sadly, that's been my experience for years in IT, at least where I live in the US.
I rarely encounter an IT person who knows what Linux is beyond "a hacker OS" or some arcane system from the 80's that's still running deep in a basement somewhere.
FOSS = janky freeware in their minds. They've usually never even heard of XCP-ng, OpenShift, TrueNAS, Bitwarden, PFSense, or any of the other professionally supported and enterprise-grade open source technologies.
-
@Lettuceeatlettuce okay, glad you still have a job at least. Sick that they're giving you those towers! It'd be a field day for me, I hope you enjoy it!
For sure! 🫶
-
I don't think feeling sad in this situation is dumb at all
I'm with you in your pain Linux brother/sister... I'll drink a pint in your name tonight
Thank you, I might join in spirit heh
-
Shutdown: noun
Shut down: verb
You can't straddle the lane.
Harsh but fair, edited lol.
-
Start job hunting now. By the sound of it they are one of those PE firms that zombie walk every acquisition into mediocrity.
For sure, I'm on it already.
-
Got everything saved already. They are wiping my Linux laptop Wednesday and putting Windows 11 on it. Looking forward to my sleek and fast Thinkpad to get much slower and clunkier.
Oh buddy they’re wiping your laptop that sucks. Figured you were talking like servers and stuff (which is still bad.) if it’s company issued you don’t have a choice, but do they allow personal hardware to be connected? If so I’d just go buy my own thinkpad.
-
I feel you so much on this. Bet your work was really cool.
What cool FOSS things would you do first if this take-over company allowed you to?
Good question. I was in the process of testing out DokuWiki for internal documentation, that was really cool.
But probably using Tailscale to phase out our janky ipsec VPN solution. Super high speed and bandwidth aren't a concern at my current place, so Tailscale would be a great solution to fix the current setup we have and make remote work much easier for end users.
I was looking at a Grafana/Prometheus stack for active monitoring and metrics too, which would have been really cool.
I was also talking to the former owner about developing an in-house piece of software that used machine learning and OCR to pull relevant data out of huge construction PDFs, convert it to CSV formatted data, and import that directly into our estimating software, saving our estimators massive amounts of time having to manually parse those documents and input the data line by line, cell by cell.
-
Oh buddy they’re wiping your laptop that sucks. Figured you were talking like servers and stuff (which is still bad.) if it’s company issued you don’t have a choice, but do they allow personal hardware to be connected? If so I’d just go buy my own thinkpad.
Yeah, it really bites. And no, they don't allow anything personal other than phones.
At least I get to use the Thinkpad, even if it is gimped with Windows. They initially weren't even going to allow that, because their company deploys only HP laptops.
But I made a strong and slightly pathetic case to the manager and he relented. Angry that I had to kiss the ring, but right now I need the money, and I really hated their clunky HP laptops.
-
Yeah, it really bites. And no, they don't allow anything personal other than phones.
At least I get to use the Thinkpad, even if it is gimped with Windows. They initially weren't even going to allow that, because their company deploys only HP laptops.
But I made a strong and slightly pathetic case to the manager and he relented. Angry that I had to kiss the ring, but right now I need the money, and I really hated their clunky HP laptops.
Can you run WSL or whatever it’s called? I se to remember some coworkers getting a Linux shell on windows. Of course that still leaves you with the shitty windows UI.
-
I tried to push back, but they are a much larger company and they made it clear that I would be playing by their rules, not mine.
I was thinking of quitting immediately, but at least in my region of the country, the IT market is really rough right now, so I can't afford to be out of work for months.
I won't last long here though. They are half owned by a private equity firm, so they run everything based on the bottom line. Their IT team is understaffed, underpaid, and they are always looking for excuses to lay folks off or fire them. Their turnover rate is pretty high, burnout is rife.
I know it's rough. Trying to find a job that pays well and isn't deep into proprietary stuff like SQL Server, C# and alike. Sadly this scenario is overwhelmingly the case, and until the crowdfunded and open source scenario get strong (they still aren't) there isn't too much of an option.
-
Depends on where you work and what their policies are. My work does have many strict policies on following licenses, protecting sensitive data, etc
My solution was to MIT license and open source everything I write. It follows all policies while still giving me the flexibility to fork/share the code with any other institutions that want to run something similar.
It also had the added benefit of forcing me to properly manage secrets, gitignores, etc
I don't know where you are, but this isn't always enough. If it's your employer's IP it's not yours to license to begin with.
In my situation, it even extends to any hobby projects I work on and I don't think my situation is unusual.
That said, most employers don't care about hobby projects with no earning potential.
-
I am careful, but not concerned. The new company's IT doesn't give a damn about anything that I set up or implemented. Their reactions when I was describing my work and job role before the buyout was essentially, "Aww, the cute little sysadmin was making scripts and using Linux, isn't that sweet."
As far as they're concerned, all the old hardware and software are e-waste and are being scrapped. They are ripping out everything, literally. From our phone system, to our physical devices, to our firewalls, network switches, Active Directory, and file server.
They are replacing every single part of our infrastructure. Everything I built is useless in their eyes.
It's incredible how that proprietary software is actually inefficient e-waste. Most FOSS isn't bloated or slow, but proprietary software got the high ground because of contracts and "security", I'm sure.
