You put lots of time and effort in. Now it will be discarded due to decisions of others.
Sad and/or disappointed feelings are normal.
Take care of yourself.
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
You put lots of time and effort in. Now it will be discarded due to decisions of others.
Sad and/or disappointed feelings are normal.
Take care of yourself.
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.
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.
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 …
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.
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.
Thanks 🤜🤛
it feels sucky to see all my hours of hard work getting trashed without a second thought.
I'm an electronic security installer. You know how many times I've done stuff like install a complete 40+ camera CCTV system at a new store under construction only to be back at the same store a year later ripping it all out when it goes out of business? I know what that feels like.
Worst is when you come around for a regular store equipment refresh and recognize something you installed at that store ten years ago and start feeling real old...
Good luck wherever life takes you now.
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.
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.
Many years ago I did post mix installs. Because we were subcontract, it was not unusual to install a system for one company, then replace it under the banner of another company, and then rip that out and install another system on behalf of the first company again.
I can think of at least 3 different venues in our CBD that I swapped like that.
What it did was make me real good at ensuring anything I installed was easy to follow and work with afterwards... Cause it was probably going to be me again lol
My job title is "Linux System Administrator". I'd quit if they tried to make me drop Linux.
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.
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. Probably most computers in the world are using OpenSSL or GNUTLS.
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.
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!
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.
For sure, already reaching out to recruiters and applying to some job postings.
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.
Sadly, something we all have to get used to. Everything we do is ephemeral and the next guy will likely have better/different ideas on how to do things.
Basically everything I've ever built has been torn down or somehow bastardized eventually.
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.
That sucks. I know what it’s like to feel like the only voice of reason when your company is shooting itself in the foot.
I see from other comments you’re already looking for a new job, which is a very good idea. From your description of this buyout, it seems very likely that you’re about 6 months to a year out from the layoff stage of the private equity playbook.
At the end of the day you’ll always have the experience you gained from building all that stuff. Perhaps you’ll get a chance to build it back even better somewhere else!
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.
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. 😮💨
That's unfortunate. Both for throwing out all of your work and replacing it with an objectively inferior solution with poor track record of long-term sustainability.
This won’t be the last time, I’m afraid. At the end of the day, software developers build sandcastles.
If you want to build something that will outlast your company, make sure you also have a hobby or craft outside of computing.
Your feelings are valid, that blows.
Thank you 👊
At least you learned a lot along your journey, while getting paid for it. So it's not entirely a waste of time.
Shutdown: noun
Shut down: verb
You can't straddle the lane.
Harsh but fair, edited lol.
Absolutely feel you, kinda similar situation at work atm. What frustrates me the most is that none of the IT personnel understands my frustration because most are not in that kind of IT community and don't share the ideas behind all that. Just here to earn a dollar, whatever system we're working on. No intrinsic desire to make the world better or at least more secure, none of that. Just robots and bureaucrats.
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.
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.
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.
foss forever, brother
Absolutely 👊
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.
At the end of the day, they are just digital things. You had some great learning experiences with them. Now it's time to put those skills to use, and learn what's next that makes you happy.
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
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.
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.
@Lettuceeatlettuce such a sad story! I'm assuming you're finding new work? I hope you're able to take your Linux/FOSS skills somewhere they'll be appreciated
You're welcome to join me.
Thank you for your service 🫡