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 shut down 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 shut down, 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! ✊

Edit: Thanks, everybody so much for the kind words and advice!

  • @MNByChoice@midwest.social
    link
    fedilink
    20029 days ago

    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.

  • @ad_on_is@lemm.ee
    link
    fedilink
    English
    2128 days ago

    At least you learned a lot along your journey, while getting paid for it. So it’s not entirely a waste of time.

  • Captech
    link
    fedilink
    1029 days ago

    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

  • 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.

  • @neidu3@sh.itjust.works
    link
    fedilink
    English
    7129 days ago

    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.

    • brandon
      link
      fedilink
      English
      66
      edit-2
      29 days ago

      Please be careful when copying anything that could be considered your employer’s intellectual property (almost certainly anything you built as an employee falls into this category) 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).

      • Lettuce eat lettuceOP
        link
        fedilink
        3029 days ago

        I am careful, but not concerned. The new company’s IT doesn’t give a damn about anything that I set up or implemented. Their reactions when I was describing my work and job role before the buyout was essentially, “Aww, the cute little sysadmin was making scripts and using Linux, isn’t that sweet.”

        As far as they’re concerned, all the old hardware and software are e-waste and are being scrapped. They are ripping out everything, literally. From our phone system, to our physical devices, to our firewalls, network switches, Active Directory, and file server.

        They are replacing every single part of our infrastructure. Everything I built is useless in their eyes.

      • @neidu3@sh.itjust.works
        link
        fedilink
        English
        1129 days ago

        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.

      • @Verqix@lemmy.world
        link
        fedilink
        2229 days ago

        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.

        • @JuxtaposedJaguar@lemmy.ml
          link
          fedilink
          629 days ago

          I don’t know if there’s any precedence for this, but I could see a court asking to see the git commit log if things went that far.

      • Dran
        link
        fedilink
        1129 days ago

        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

        • @folekaule@lemmy.world
          link
          fedilink
          929 days ago

          I don’t know where you are, but this isn’t always enough. If it’s your employer’s IP it’s not yours to license to begin with.

          In my situation, it even extends to any hobby projects I work on and I don’t think my situation is unusual.

          That said, most employers don’t care about hobby projects with no earning potential.

    • Yeah. I retired a year ago, every now & then I say to myself “I’m sure I had a script for that…” bit then I can’t find it of course, which makes me sad.

      Oh & I used to sign in to GitHub with a username & password, then GitHub said I needed to change my password, and emailed me a link to my old work address, which I can no longer access.

      So I’m going to have to fork my own stuff!

    • @toynbee@lemmy.world
      link
      fedilink
      2229 days ago

      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)!

      • Lettuce eat lettuceOP
        link
        fedilink
        17
        edit-2
        29 days ago

        My work laptop is a Thinkpad running Debian with the Plasma DE, I love it so much. Everything is snappy and clean, set up and tuned perfectly to my preferences.

        It’s getting wiped in a few days. I requested to keep it as a personal device if I wiped it, they denied that request. I even offered to buy it back from the company, but still no.

        At least I get to keep it instead of using their bulky, crappy HPs, but replacing my sleek Debian system with Windows 11 feels so wrong.

      • 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)!

        Yeah, IT fleet upgrades are a great way to snag some decent hardware for dirt cheap. My Plex server is running on an old HP EliteDesk that came from a cubicle. The hardware itself is often practically new, because corporate drones rarely do anything intensive enough to actually push the hardware. Just give it a quick spray with some canned air, and pop a new drive in.

    • Lettuce eat lettuceOP
      link
      fedilink
      4429 days ago

      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.

      • @vanderbilt@lemmy.world
        link
        fedilink
        3729 days ago

        Start job hunting now. By the sound of it they are one of those PE firms that zombie walk every acquisition into mediocrity.

      • @scoredseqrica@lemmy.ml
        link
        fedilink
        328 days ago

        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!

  • @Jhex@lemmy.world
    link
    fedilink
    2929 days ago

    I don’t think feeling sad in this situation is dumb at all

    I’m with you in your pain Linux brother/sister… I’ll drink a pint in your name tonight

  • @VeryVito@lemmy.ml
    link
    fedilink
    3029 days ago

    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.