Being Forced to Say Goodbye
-
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!
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.
-
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.
25 years ago the system was setup as a quick temporary solution.
-
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 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).
-
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).
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.
-
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 get it. I've just been through a merger and the new head software delivery has plans on rewriting everything in their tech stack. He is in for an absolute fucking ride when he realises that such a rewrite will not take a year but 5 to 10 and will incapacitate our department for the entire time. In a rapidly evolving market. It is 3 decades of continuous and rapid feature expansions he's trying to unroll.
It's not FOSS though, so I'm not as invested in it, I'm just here to see him either fail utterly or get kicked due to his cognitive dissonance that'll cost our department in the tens or hundreds of millions.
-
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!
This is why I stopped giving a shit at work and not spending all the extra effort. It all just gets killed by some manager that doesn’t know what the hell they are talking about.
-
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 …
-
Now be prepared for windows nagging you to update everyday
- but corporate policy is to let IT handle updates
- but Windows doesn’t like being ignored so it bypasses group policy and auto-updates
-
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!
Thank you for your service 🫡
-
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.
-
Yeah, the corporate style has already taken over. None of the new IT guys are mean or nasty, but they just don't care about FOSS. It doesn't even register with them.
Talking about all my integrations is just met with blank stares and, "Linux huh? I remember learning a bit about that 10 years ago in tech school."
It's just not even on their radar.
that's actually really sad, IT of all people don't care about FOSS?
-
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!
it sucks that they teach us our code will live forever, so watch out for introducing bugs....
then the companies go under, designs change and you waste your life leaving behind nothing.
-
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 not dumb.
It's devastating.
I'm not a linux user due to multiple of reasons and I'm sad about it.
I'd be very sad if I was able to make it to the other side and then get taken back -
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).
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
-
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!
It's natural to feel sad seeing your work undone. Start searching for a new gig and do the best you can to not have an emotional response to the stuff you dislike; that'll only make you exhausted and burned out.
I'm sorry your job got worse. Try to find where you can be happy again.
-
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!
My job title is "Linux System Administrator". I'd quit if they tried to make me drop Linux.
-
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!
Your feelings are valid, that blows.
-
My job title is "Linux System Administrator". I'd quit if they tried to make me drop Linux.
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)!
-
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).
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.
-
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).
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...
