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 shut down 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 shut down, 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! ✊
Edit: Thanks, everybody so much for the kind words and advice!
At least you learned a lot along your journey, while getting paid for it. So it’s not entirely a waste of time.
Well… shit. My company just sold my department to another company. The phrase they use in the office is “a Microsoft shop”. We’re talking Windows, Teams, Azure and O365.
The transition is going to be shit. After the transition is over, it will be shit.
I might just operate my workflow entirely out of WSL2 out of spite.
I feel simultaneously good and bad that the least modern team at my company is the Windows admin team. I hope they were embarrassed as shit when they were asked how that automated process I help them create 9 months ago was going and they said, “Uh, we’ll be rolling it out this quarter.” They’re constantly at least 2 steps behind our Linux admins.
Teams is its own plane of hell. Sorry to hear.
I work at a “Microsoft Shop” in a division that was a previously acquired software developer that used and entirely linux based dev stack.
That stack is still all linux and we basically have to do all our work in WSL. It’s a pain.
This won’t be the last time, I’m afraid. At the end of the day, software developers build sandcastles.
If you want to build something that will outlast your company, make sure you also have a hobby or craft outside of computing.
You put lots of time and effort in. Now it will be discarded due to decisions of others.
Sad and/or disappointed feelings are normal.
Take care of yourself.
I think we (as an industry) need to be honest to ourselves and admit that pretty much everything we’re building is temporary. And not in a philosophical sense. 90% of the code I wrote in my about 10 years of professional work is probably gone by now - sometimes replaced by myself. In another ten years, chances are not a single line of code will have survived.
Everything is temporary, except for that 25 year old system that’s keeping everything running and can’t be replaced because nobody knows how or why it works just that if you touch it everything falls over.
The more magic switch perhaps?
25 years ago the system was setup as a quick temporary solution.
original generation of COBOL programmers where expecting their programs to be replaced (or at least rewritten) within a decade or so – and then Y2K and we realized how much COBOL was still in the wild – and now a couple decades down the line, they’re still having problems trying to convince fintech to switch from COBOL to the new language of Java …
Even that is pretty temporary.
If you build a house, there’s a good chance, it will survive for decades or even centuries. The house I currently live in survived two world wars and heavy bombardment in one of them. I don’t think any software will manage that.
But there are different types of temporary. Temporary because the code got updated/upgraded or new and better software got implemented feels fine. It feels like your work was part of the never ending march of technical progress. Temporary because it gets ripped out if favor of a different, inferior suite hits hard.
If my code gets superseded by someone else’s complete rewrite that is better, then I’m all for it. If my code gets thrown out because we’re switching to a different, inferior system that is completely incompatible with my work, then that just hits like a ton of bricks.
Thanks 🤜🤛
Start your own company :-)
it feels sucky to see all my hours of hard work getting trashed without a second thought.
I’m an electronic security installer. You know how many times I’ve done stuff like install a complete 40+ camera CCTV system at a new store under construction only to be back at the same store a year later ripping it all out when it goes out of business? I know what that feels like.
Worst is when you come around for a regular store equipment refresh and recognize something you installed at that store ten years ago and start feeling real old…
Good luck wherever life takes you now.
Sorry to hear that, sounds rough too! Thanks for the well wishes, I’m talking with a few different recruiters right now and applying to some positions.
Still have my job currently, but hopefully I can make the jump soon to a Linux environment.
I was assigned the installation of a whole industrial line for food packaging, multiple millions worth, on and off I spent like 8 months abroad forcing badly designed machines into working (I was the top tech and I resigned after this job), even ended up in the hospital, likely due to stress. Few months after I left, I go out drinking with a former colleague who had been on site with me, he says: “Well, I’m happy to inform you that, the customer hasn’t called us for months! Means everything’s working, great job!” and shook my hand.
The following morning, another former colleague sends me the screenshot of a mail from the customer saying that the business opportunities didn’t work out and they’re decommissioning the line. Literal blood, sweat and tears, completely wasted.
Many years ago I did post mix installs. Because we were subcontract, it was not unusual to install a system for one company, then replace it under the banner of another company, and then rip that out and install another system on behalf of the first company again.
I can think of at least 3 different venues in our CBD that I swapped like that.
What it did was make me real good at ensuring anything I installed was easy to follow and work with afterwards… Cause it was probably going to be me again lol
That sucks. I know what it’s like to feel like the only voice of reason when your company is shooting itself in the foot.
I see from other comments you’re already looking for a new job, which is a very good idea. From your description of this buyout, it seems very likely that you’re about 6 months to a year out from the layoff stage of the private equity playbook.
At the end of the day you’ll always have the experience you gained from building all that stuff. Perhaps you’ll get a chance to build it back even better somewhere else!
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.
Please be careful when copying anything that could be considered your employer’s intellectual property (almost certainly anything you built as an employee falls into this category) 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.
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.
I always advocate for FOSS solutions at my work, but most of the time I get shut down with some variation of “We prefer $MSP’s solution because it gives us someone else to blame if shit hits the fan”. I hate that sentiment, but I appreciate the honesty.
“But it wouldn’t hit the fan so much if we stopped using Microsoft’s half-baked products!”
It always falls on deaf ears. I can’t believe how many millions my employer throws at Microsoft every year just to complain about how broken it is.
But it’s also difficult to prove you didn’t make it similarly 2 times. Just do some name changing, reordering and some slight changes and you should be golden.
I don’t know if there’s any precedence for this, but I could see a court asking to see the git commit log if things went that far.
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.
That seems like a good idea.
True. In my particular case it’s not an issue (because of a long and boring story I can’tbe arsed getting into), but shielding oneself as well as the employer from legal liability is important.
Sadly, this means all my Linux and FOSS implementations I’ve worked on
Please be careful when copying anything that could be considered your employer’s intellectual property
Very unlikely $NEW_EMPLOYER will run all your ideas past $OLD_EMPLOYER to see if it’s their code…
Will they even know if they are throwing it all away?
Already backed up securely and anonymously :)
Yeah. I retired a year ago, every now & then I say to myself “I’m sure I had a script for that…” bit then I can’t find it of course, which makes me sad.
Oh & I used to sign in to GitHub with a username & password, then GitHub said I needed to change my password, and emailed me a link to my old work address, which I can no longer access.
So I’m going to have to fork my own stuff!
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.
Sadly, something we all have to get used to. Everything we do is ephemeral and the next guy will likely have better/different ideas on how to do things.
Basically everything I’ve ever built has been torn down or somehow bastardized eventually.
the next guy will likely have better/different ideas on how to do things. The extra fucked up part comes when the “new guys” purge all the people and systems that were already working and proven end up just circling around to more or less the old things. While of course acting like it was all their “ideas” after spending more money than was ever needed. The workers get fucked and the undervalued knowledge is lost (and the new workers also get fucked by being underpaid and overworked themselves). So fucking done with how much the wasteful executives giving themselves bonuses and keep cutting more and more corners.
Check your formatting
That’s unfortunate. Both for throwing out all of your work and replacing it with an objectively inferior solution with poor track record of long-term sustainability.
My job title is “Linux System Administrator”. I’d quit if they tried to make me drop Linux.
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.
For sure, I’m on it already.
Everything based on the bottom line
Using azure.
Pick one! I know why they’re a full Microsoft organisation, you’re already using office and exchange, so 365 makes sense, then teams makes sense, then may as well have some sharepoint storage, power platform is snazzy, and then oops we’re full azure hosted. I get why, it’s very convenient, has some good ecosystem integration benefits for the user and all the rest, but it certainly isn’t cheap.
Anyway, I’m sorry they’re kicking Linux and trashing years of hard work. That really sucks. Sadly new job time I think. But that’s easier said than done these days. Best of luck!
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.
I’d argue that most mainstream FOSS is extremely strong. Something like 80% of servers and 60% of smartphones run Linux. Up until recently, Cloudflare was using Nginx for their entire CDN. The thing they replaced it with is technically also FOSS. Probably most computers in the world are using OpenSSL or GNUTLS.
I think the real “weakness” of FOSS is that they don’t have the money or the desire to schmooze corporate decision makers. They also don’t have sexy GUIs, but anyone could contribute that if they wanted.
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)!
My work laptop is a Thinkpad running Debian with the Plasma DE, I love it so much. Everything is snappy and clean, set up and tuned perfectly to my preferences.
It’s getting wiped in a few days. I requested to keep it as a personal device if I wiped it, they denied that request. I even offered to buy it back from the company, but still no.
At least I get to keep it instead of using their bulky, crappy HPs, but replacing my sleek Debian system with Windows 11 feels so wrong.
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.
My org recently declared that all remote access to “Office” must be through OS-X or Windows for “security reasons.” So, they put a check on browser IDs and if your browser IDs as being on Linux, they harass you for password re-entry every 90 seconds. Of course, Chrome Network Conditions tab allows you to choose what your browser IDs itself as running on…
That’s a damn shame, I’m sorry! I hope you got to back up a few of your personal things, and if you didn’t at least you have a bunch of knowledge to take onto your next project
It’s not dumb to feel sad about it. Enshittification is sad, especially when you see it from the inside.
Quit?
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.
