Being Forced to Say Goodbye
-
@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!
-
It's not dumb to see something you've worked and put your heart on being gutted to make room for some bullshit.
-
Yo, that's not being dumb. That's a legitimate complaint. The OS you use is a tool you use to effectively do your job. A welder would equally be upset if their boss swapped out their welder for an inferior one they are less familiar with.
-
foss forever, brother
-
Yeah, I had some cool Ansible integrations, Docker containers running internal infrastructure monitoring, OSTicket FOSS ticketing system, Open Project for project management, Tailscale for secure remote access, etc.
Oh well, I got a bunch of great experience building it, and I can still use that stuff on my own infrastructure at home.
-
I’m sorry, friend.
If any of those deployments included code you or your team wrote, I highly encourage archiving it in VCS somewhere, even if only internally.
Also do a formal write up of all the deployments and why each tech choice was made.
Your hard won knowledge and skills should be preserved somewhere.
-
And at your next job, at an employer who sees the value of FOSS and a nerd with strong Linux-fu!
-
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.
-
Now be prepared for windows nagging you to update everyday
-
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.
-
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.
-
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.
-
Absolutely
-
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.
-
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.
-
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.
-
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.
-
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.
-
My current work is going through this
They dropped an open system we used but the team managing the new one is so bureaucratic and disconnected from the people actually doing work it’s ridiculous.
They reject every proposal/change unless it’s 100% perfect. I had a project delayed by four weeks because I didn’t end single line docstrings with periods. They didn’t review the substance of the pr, they just commented on the docstrings and stopped as if the rest had no merit. It was two weeks between review cycles, so it took three cycles to actually fix what could have been one.
They blocked a 10 row lookup table because it wasn’t indexed and wouldn’t have suitable performance. That held me up for 2 weeks because they wanted me to profile it and document the lack of an index (it had no measurable impact, in case you were wondering).
That whole team is just clearly a make work program. They nitpick and bike shed on every issue. But they aggressively document all the make work they do so they look super busy and important to the execs.
I just want to get work done, but instead it’s a Sisyphean effort.
-
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.
