• Scratch@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    7
    ·
    2 days ago

    “I don’t understand this code, but I can make it better!”

    That’s the sound of humiliation getting ready to visit.

  • Treczoks@lemmy.world
    link
    fedilink
    arrow-up
    45
    arrow-down
    1
    ·
    3 days ago

    If you think migrating off COBOL is bad, imagine how bad moving off COBOL with AI generated code slob will be.

    • pivot_root@lemmy.world
      link
      fedilink
      arrow-up
      19
      ·
      3 days ago

      Ah, but you see: that’s somebody else’s problem. He’s not going to be the sucker left dealing with an unmaintainable pile of brittle slop, so it’s totally fine /s

    • Radium@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      5
      ·
      3 days ago

      This. And it’s not like it’s Python or something with a bunch of online / open source content that the model can be trained on. COBOL is probably the least open sourced or publicly talked about language.

  • InFerNo@lemmy.ml
    link
    fedilink
    arrow-up
    16
    ·
    3 days ago

    “which would likely require the use of generative AI”. Why? Why does it “likely” need that? Have developers become stupid? Have decent analysts fallen off a cliff?

    • xor@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      7
      ·
      3 days ago

      nope, but poser developers have sprung up and management is using it to negotiate the price of developers down….
      the point of this is to completely break it though, there’s no way they’re stupid enough to think that might work…

        • xor@lemmy.dbzer0.com
          link
          fedilink
          English
          arrow-up
          2
          ·
          1 day ago

          turns out the ai apocalypse was just a bunch of psychos ruining everything by shoving vaporware ai slop into everything… welp, start a garden…
          i hear you can farm infinite tilapia in a swimming pool…. and they eat anything…

  • softcat@lemmy.ca
    link
    fedilink
    English
    arrow-up
    47
    ·
    3 days ago

    Not just migrate, but quickly. Move fast and break things crowd demands it.

  • Davin@lemmy.world
    link
    fedilink
    arrow-up
    10
    ·
    3 days ago

    As someone who was part of a team that moved a company off of a mainframe into the modern world of technology (about ten years ago). It takes years.

    I guarantee that this is going to go badly. It’s going to take much longer than they think. And it’s going to be very expensive.

    But I also guarantee that they don’t care. It seems they’re more than happy to weaken the US in pursuit of profit and to help Putin for some reason.

    • SirQuack@feddit.nl
      link
      fedilink
      arrow-up
      3
      ·
      edit-2
      3 days ago

      I’ve recently started working in a company that uses old tech, and there is a minor interest from me to actually follow the COBOL onboarding. It seems like a pretty cool language construct to know, alongside my years of OOP experiences with stuff like C# and Java.

      And there are still courses being offered, as it’s far from eradicated (although everyone wants it gone).

      • Davin@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        3 days ago

        It’s not a dead language. And while I don’t care much for it, only move if it makes sense. The reason the company I worked with moved, was because the servers were getting very costly to keep up, and the parts were becoming rarer. So they were concerned they might be in a situation where they’d be unable to work for up to three weeks. And they had already done some work moving several of their systems and apps to C# and virtual servers. And it still took years in order to do it with minimal disruption to business operations.

        But since the Department of dipshit doesn’t actually care about disrupting services that affect the working people, I bet they’ll do it and be like, oops, our bad, Biden made us do it.

    • Radium@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      7
      arrow-down
      1
      ·
      3 days ago

      Great metaphor.

      Don’t worry, we’ll throw the COBOL through an LLM. I’m sure LLMs are great at cobol, since there’s an abundance of content online about COBOL for it to have been trained on /s

  • SoftestSapphic@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    2 days ago

    Systems that can’t go down will never be voluntarily brought down to update them.

    This either results in nothing or the end of Social Security

  • pivot_root@lemmy.world
    link
    fedilink
    arrow-up
    24
    arrow-down
    1
    ·
    edit-2
    3 days ago

    Oh look, even more proof he has no idea what he’s doing.

    These systems are so ancient that their bugs and edge cases are expected behaviors for downstream services and applications. Properly replacing it would take years of effort, testing, validation, and communication… and this numbnuts is going to have his college interns quickly replace it by “vibe coding” something into existence with AI and flipping a switch.

    I expect the goal is to break it so badly that they can justify getting rid of social security as a whole, but if I take it at face value as DOGE trying to make things more “efficient”… that change is going to cause so many problems that it would cost a magnitude more to fix the damage they did than just leaving it the fuck alone.

  • MadMadBunny@lemmy.ca
    link
    fedilink
    arrow-up
    17
    ·
    edit-2
    3 days ago

    HAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHHAHAHAHAHAHAA HOLY SHIT, the sheer fucking hubris of delusion!!!

    Wow, I mean, holy fuck… someone’s definitely lacing his k with something

    • Crashumbc@lemmy.world
      link
      fedilink
      English
      arrow-up
      4
      ·
      3 days ago

      So many people are missing this!

      This isn’t about “fixing” anything, it is an excuse to dismantle the SSA …

      • surewhynotlem@lemmy.world
        link
        fedilink
        arrow-up
        4
        ·
        3 days ago

        It’s a common business tactic. I’ve done it myself at work.

        You go in to “fix” something. You shuffle shit around, complain how complex and expensive it is, fail too fix it, then use the added expense and time wasted to justify shutting it down.

  • humanspiral@lemmy.ca
    link
    fedilink
    arrow-up
    3
    arrow-down
    1
    ·
    3 days ago

    One semi safe approach to this is that almost all languages can be written line for line replacement “like COBOL”. There will be COBOL built in functions that need to be reimplemented. There may be internal representation differences that matter.

    In the end, there is the same unmaintainable line count code base, and it runs slower, though it may run on faster hardware to offset. This approach introduces the fewest bugs with no real advantage. Rewriting application from modern language perspective is sure to break it much harder.

    • SirQuack@feddit.nl
      link
      fedilink
      arrow-up
      1
      ·
      3 days ago

      Except COBOL has completely different number handling, so one-on-one migration will cause data corruptions.

      Might not mean much on infrequently used systems with hundreds of interactions per year, but on fundamentals like SSNs, this will kill people.

      Good programmers usually commit to ethics codes, cowboy AI “developers” usually don’t.