Being Forced to Say Goodbye
-
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.
-
that's actually really sad, IT of all people don't care about FOSS?
-
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.
-
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 -
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
-
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 job title is "Linux System Administrator". I'd quit if they tried to make me drop Linux.
-
Your feelings are valid, that blows.
-
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)!
-
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
Very unlikely $NEW_EMPLOYER will run all your ideas past $OLD_EMPLOYER to see if it's their code...
-
That's very unfortunate but hopefully you developed skills that will help you in your future career.
-
Weres crowd strike windows shitting the bed when u need it
-
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.
-
Thank you
-
For sure, I've learned a ton in the last year. Hopefully I can land a Linux focused job this year and get away from Windows support once and for all.
