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!
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
At least you learned a lot along your journey, while getting paid for it. So it’s not entirely a waste of time.
Man it does stink. Get some of them up on GitHub or Gitlab if you can.
Quit?
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.
I work at a “Microsoft Shop” in a division that was a previously acquired software developer that used an 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.
Teams is its own plane of hell. Sorry to hear.
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.
Start your own company :-)
At the end of the day, they are just digital things. You had some great learning experiences with them. Now it’s time to put those skills to use, and learn what’s next that makes you happy.
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!
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.
I feel for you. Here’s hoping the new system is clean.
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.
shutdown: commandHarsh but fair, edited lol.
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
lol thanks. It must have somehow kept the quote format from another reply I made.
Back in the 1990s I developed an app over the course of 6 years, first 3 in C/DOS then we ported that to C++/Borland/Win95 and continued developing it for another 3 years. I was the only coder, we had a dedicated tester / documentation specialist and the algorithms lead who was more of an idea guy than any hands-on code work.
We got bought out. Buyers “needed it in native Win32 because of the depth of the talent pool.” Whatever, I’m here to help if they want it during porting. Buyers estimated 2 developers could port it in about 2-3 months. Yeah, o.k. Never asked for help, but at 6 months in they had expanded the dev team to 6 guys and were still struggling and looking to hire more. Ultimately they reduced scope a little and called it “ready to use” in Win32 after about 15 months. Glad they got it “maintainable” by switching to that Win32 dev environment with such a deep talent pool to hire from, they easily spent more man hours on the port than we spent developing it in the first place.
