IBM taps AI to translate COBOL code to Java | TechCrunch
techcrunch.com
IBM's new product offering, Code Assistant for IBM Z, leverages a generative AI model to translate COBOL code to Java.

It’s not the 1st time a language/tool will be lost to the annals of the job market, eg VB6 or FoxPro. Though previously all such cases used to happen gradually, giving most people enough time to adapt to the changes.

I wonder what’s it going to be like this time now that the machine, w/ the help of humans of course, can accomplish an otherwise multi-month risky corporate project much faster? What happens to all those COBOL developer jobs?

Pray share your thoughts, esp if you’re a COBOL professional and have more context around the implication of this announcement 🙏

  • @PuppyOSAndCoffee@lemmy.ml
    1•1 year ago

    What.

    Most cobol systems have more code that doesn’t do anything vs code that actually does something.

    The grammar of COBOL + shit UI of mainframes means there is a shit ton of tribal anti pattern with each program. It is a pia to add fields and variables, so lazy programmers would just reuse something that wasn’t being used at that instant. Less work and more job security.

    What values do variables ROBERT1, ROBERT2 and ROBERT3 hold? Whatever ROBERT wanted.

    The reason why these things still exist is business laziness. They don’t know and don’t care what cobol is or isn’t doing.

    I am struck by … conversion to … Java? Really??? lol.

    • @eyy@lemm.ee
      2•1 year ago

      Most cobol systems have more code that doesn’t do anything vs code that actually does something.

      What values do variables ROBERT1, ROBERT2 and ROBERT3 hold? Whatever ROBERT wanted.

      And when that system is storing high-risk and/or sensitive data, do you really want to be the person who deletes code that you think “actually does nothing”, only to find out it somehow stopped another portion of code from breaking?

      The reason why these things still exist is business laziness. They don’t know and don’t care what cobol is or isn’t doing.

      That’s the thing - tor a risk-averse industry (most companies running COBOL systems belong here), being the guy who architected the move away from COBOL is a high-risk, high-stress job with little immediate rewards. At best, the move goes seamlessly, and management knows you as “the guy who updated our OS or something and saved us some money but took a few years to do it, while Bob updated our HR system and saved a bunch of money in 1 year”. At worst, you accidentally break something, and now you have a fiasco on your hands.

      • @PuppyOSAndCoffee@lemmy.ml
        2•1 year ago

        Org change vs vertical integration, which is worse and why in 500 words or less ;)

        Pay now or pay later…the organization is going to get kicked in the nuts.

        For industries that have the option, companies who got kicked in the nuts ten yrs ago are doing better today than those who are still waiting.

        IBM should shoulder a lot of the blame, there really is no reason why COBOL couldn’t be phased out in place except it would hurt IBM market share so it is not exactly a “thing”. In place transition to RUST should just be another section of the zOS manual.