DOGE's Plan to Rewrite Social Security's Code in Months
finance.yahoo.com
finance.yahoo.com
[1] https://oig.ssa.gov/congressional-testimony/2016-07-14-newsr...
If (citizen) send $500
rm -rf /
Won't work on IBM mainframe, its far more secure and complicated than that.If they were refactoring /cleaning up the code and porting to a modern platform - then yeah, that would be good for the future. But also a massive effort and well beyond anything that someone can parachute in and complete in weeks or months.
If it's an automated transformation from COBOL to say Java, then why? Any machine translated code is not going to be as clean as the source, which itself is probably not that clean if it is typical public sector code that has been mogrified repeatedly over the years to meet changing legislative needs.
There's no obvious reason why a machine translation to Java should be any more reliable than the original COBOL. The only obvious benefit is opening up to a greater number of coders who could make changes. But at the expense of losing the skills of the existing COBOL maintainers. My guess is it would be a wash.
The only way out is through and someone has to rip off all these bandaids. And while one is at is, might as well write this in a language known by more than a dozen overpaid graybeards.
What does it have to do with Social Security? It's the same kind of culture that worships lack of change over everything else, and as a result it is bloated and slow.
"we've put in our test comparison code, and it shows 100% mismatch, next we're starting on implementation"
and then later "we're at 10% mismatch, and here's the interesting bugs and issues with social security holding up the next 5%"