But then all of this has been known for decades. There are plenty of well-known techniques for how to do all that. If they haven't actually done it by now, it's a management problem, and no AI tech is going to fix that.
Watsonx: IBM's code assistant for turning COBOL into Java
21–30 of 186 posts
Re: Watsonx: IBM's code assistant for turning COBOL into Java
#22Re: Watsonx: IBM's code assistant for turning COBOL into Java
#23These systems have not been running untouched for 60 years. Regulatory environments change almost constantly and the code has to be updated accordingly. I don’t personally know anyone writing COBOL but I’m certain there’s plenty of people doing it. And to change the code you have to know it. So there’s really no 60 year old code that no one knows anymore. Also, at this point, if you are running on a dead platform and…
Re: Watsonx: IBM's code assistant for turning COBOL into Java
#24Regarding IBM's use of technology widely known for hallucinating to translate sensitive source code: it sounds weird you think the primary objective here is to deliver something that properly translates from one language to another. But it is not - the primary objective is to get money from customers and investors. Delivering something that works is secondary, and honestly, optional. Many things in IT start making a…
Especially for IBM! See IBM Watson for details.
Re: Watsonx: IBM's code assistant for turning COBOL into Java
#25The article title is clickbaity, but the actual point is the proposal of using LLMs to translate large amounts of legacy COBOL systems to more modern languages like Java. Doesn't seem terribly useful to me. I expect you could get a 90% solution faster, but the whole challenge with these projects is how to get that last bit of correctness, and how to be confident enough in the correctness of it to actually use it in P…
Re: Watsonx: IBM's code assistant for turning COBOL into Java
#26Earlier quoted context omitted.
I’d be curious to know how we’re defining “overpaying” here. These companies have effectively accrued 50+ years of technical debt (they could have migrated off COBOL decades ago). Meanwhile, based on my limited experience with these industries, I’d be surprised if they even offer market rates to new hires.
Let me up the ante. Why do we believe COBOL is yech-debt?
Those COBOL applications will keep working until the sun burns up or inflation makes the numbers so long they no longer fit in bounds.
The java applications they write should fill you with terror.
Re: Watsonx: IBM's code assistant for turning COBOL into Java
#27The article title is clickbaity, but the actual point is the proposal of using LLMs to translate large amounts of legacy COBOL systems to more modern languages like Java. Doesn't seem terribly useful to me. I expect you could get a 90% solution faster, but the whole challenge with these projects is how to get that last bit of correctness, and how to be confident enough in the correctness of it to actually use it in P…
How hard is it to actually learn COBOL? It seems like a fairly simple language to pick up, but maybe the idiomatic COBOL used in these legacy systems is particularly nasty for some reason.
Re: Watsonx: IBM's code assistant for turning COBOL into Java
#28The flawed "economic analysis" in this article is so commonly brought out, but at this point we should just call it what it is: lying. There is no "shortage of COBOL programmers." Businesses are simply choosing what they will pay, and the market is responding appropriately. And this is also not just a case of naively shouting "duh, just pay them more" for a market that can't bear the increase in costs (i.e. some indu…
Re: Watsonx: IBM's code assistant for turning COBOL into Java
#29There seems to be plenty of cobol transpilers - anybody know why they can’t use those. Immediate thought was it’s just beating on the dead Watson horse.
If they worked as effectively as they were touted, they'd have cleared out the cobol.
The issue with COBOL is any old idiot can't write it. If someone is touching the COBOL they are going in and making minor changes/expansions to an application that is older than the average HN user and those changes and expectations are well defined.
With Java and/or language of the day your cheapest run of the mill contractor given exceptionally poor instructions will crank out X LOC per day where X is the required output for them to keep their job. Maintaining that code will be some other bastards problem.
Re: Watsonx: IBM's code assistant for turning COBOL into Java
#30If it's so valuable to the industry that they have good people who know it, that should surely be reflected in the salary / comp for roles... And if that were high, people would learn it, but it's not high, it's arguably worse than just learning a little JavaScript