Being Forced to Say Goodbye
-
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.
-
25 years ago the system was setup as a quick temporary solution.
-
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.
-
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.
-
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.
-
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 …
-
- but corporate policy is to let IT handle updates
- but Windows doesn’t like being ignored so it bypasses group policy and auto-updates
-
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.
