• 👍Maximum Derek👍
    link
    fedilink
    English
    471 month ago

    Are we still calling it Y2k38? I think it needs some rebranding or we won’t be able recruit devs to put in the overtime to fix it so history can decide it was all fake.

      • @TexasDrunk
        link
        91 month ago

        Well you won. I’m headed in to work tomorrow to get started on marketing it to the C suite using this.

        • @NegativeInf
          link
          31 month ago

          I look forward to the coming developments.

    • HubertManne
      link
      fedilink
      81 month ago

      I was part of y2k rememdiation and we did some stuff for the next leap year as well and I had heard about work being done for future things. Im not in it anymore but im wondering if some is already done. Thing about y2k is it was a time when the backbone stuff was never upgraded. Banks using mainframes running cobol programs and such. Now it feels like every company changes their software yearly.

        • @ChickenLadyLovesLife
          link
          English
          31 month ago

          I worked for a large chemical additives company in the late '90s and wrote an IE6 web application (using classic ASP and Visual Basic 5) that was a front end to the company’s near-useless COBOL mainframe app that contained all of their testing and production processes and dated to the 1970s. They’re still using my application today, which means they’re still using that fucking COBOL app and the mainframes as well.

      • Blaster M
        link
        English
        11 month ago

        I remember 02/29/2000, the day that didn’t exist. We did 02/28/2000 twice.

    • @jaybone
      link
      41 month ago

      I’ll just wait for Crowdstrike to deploy a fix.