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!

  • leisesprecher@feddit.org
    link
    fedilink
    arrow-up
    62
    arrow-down
    1
    ·
    4 days ago

    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.

    • schizo@forum.uncomfortable.business
      link
      fedilink
      English
      arrow-up
      56
      ·
      4 days ago

      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.

        • cerement@slrpnk.net
          link
          fedilink
          arrow-up
          13
          ·
          4 days ago

          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 …

      • leisesprecher@feddit.org
        link
        fedilink
        arrow-up
        7
        ·
        4 days ago

        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.

    • astronaut_sloth@mander.xyz
      link
      fedilink
      English
      arrow-up
      14
      ·
      4 days ago

      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.