The problem isn't that they don't know COBOL. The problem is they're not asking questions about things they don't understand. That's very dangerous in legacy code environments.
Maybe this is a dumb question, but why would they have to make changes to cobol at all if there stated goal is to reduce spending? Wouldn’t it be more like figure out the outflows and just auditing spending and then turning some off?
So many Elon threads, some with conservative defenders, no mention of Chesterton’s fence by anyone, when it’s so apt.<p>More importantly, Chesterton’s fence is a conservative idea. And it’s an important idea. I am not a conservative, but I am not a total idiot so I can appreciate the wisdom of _not tearing down the fence without understanding why it’s put up there._
I tested it and it turns out LLMs can follow commands such as "Port the following Python code to COBOL", although it's certainly harder to validate the output is correct.