Being Forced to Say Goodbye
-
Oof, that's rough. My spouse is a software engineer and has been through a similar thing recently.
Based om all the replies in this post it seems like it happens quite a lot. Or it all just happens now for some reason...
-
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.
My last job was Windows desktop, so I installed vmware and ran Linux in fullscreen mode.
-
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!
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.
-
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
-
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.
That last thing. Can you do it under an Open License and put on git?
Seems like an improvement for all. -
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.
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 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.
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 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.
-
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.
Teams is its own plane of hell. Sorry to hear.
-
Teams is its own plane of hell. Sorry to hear.
-
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.
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!
-
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 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.
-
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!
Man it does stink. Get some of them up on GitHub or Gitlab if you can.
-
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!
At least you learned a lot along your journey, while getting paid for it. So it's not entirely a waste of time.
-
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!
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
-
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.
Wow. You have some really cool quick-improvenent ideas alongside major improvements. OCR would have applications in so many other situations too!
It definitely sounds like you will be under-appreciated under the new owners, you have so much skill and knowledge that are kinda going to waste with them.
But based on your other comments here, you know this too. Best wishes and good luck in your search.
-
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?
-
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.
-
Check your formatting
lol thanks. It must have somehow kept the quote format from another reply I made.
-
That last thing. Can you do it under an Open License and put on git?
Seems like an improvement for all.If I am ever able to build it and get it working reasonably well, for sure!
