DOGE Plans to Rebuild SSA Codebase in Months, Risking Benefits and System Collapse
-
This post did not contain any content.
If it fails spectaculairly who will take the blame? Will there be any repercussions at all?
Or will Musk and Trump shrug their shoulders? Halfheartedly blame Biden for badly programming the original database then go play some golf/videogaminges?
-
This post did not contain any content.
That’s the idea. Then they say anyone who complains about not receiving benefits is a fraud.
-
Ah yes, a classic tale...
"We're going to take this perfectly efficient and functional COBOL code base and rewrite it in Java! And we'll do it in a few months!"
So many more competent people and organizations than them have already tried this and spectacularly crashed and burned. There's are literal case studies on these types of failed endeavors.
I bet they'll do it in Waterfall too.
It's interesting. If they use Grok, this could well be the deathknell for vibe programming (at least for now). It's just fucking traffic that their hubris will cause grief and pain to do many Americans - and cost the lives of more than a few.
Functional, yes. But rarely are these sorts of things efficient. They’re covered in decades of cruft and workarounds.
Which just makes them that much harder to port to a different language. Especially by some 19 year old who goes by “Big Balls”
-
This is just another step down "I honestly just can't comprehend the stupidity of what is going on in the American government"-alley...
Like... what do they even expect to come of this? Why are they even interested in doing it? Is it just to stir up shit?
They are trying to break the government beyond all repair. At that point they'll say it's the Democrats that broke it.
Their cult members will swallow the lie hook line and sinker, and continue to keep them in power. (Side note, this will be made easier by gutting all election oversight as part of the package.)
Meanwhile, all that tax money we paid into Social Security, SNAP, Medicaid and Medicare, Unemployment insurance... basically any program meant to help people, will flow directly into billionaire's pockets.
-
Ah yes, a classic tale...
"We're going to take this perfectly efficient and functional COBOL code base and rewrite it in Java! And we'll do it in a few months!"
So many more competent people and organizations than them have already tried this and spectacularly crashed and burned. There's are literal case studies on these types of failed endeavors.
I bet they'll do it in Waterfall too.
It's interesting. If they use Grok, this could well be the deathknell for vibe programming (at least for now). It's just fucking traffic that their hubris will cause grief and pain to do many Americans - and cost the lives of more than a few.
-
This post did not contain any content.
If you want the source of any future "technical glitches", it's this wilfully negligent act. Courts, take note.
-
Jokes aside, nothing wrong with rewriting in Java. It is well-suited for this kind of thing.
Rewriting it in anything without fully understanding the original code (the fact they think 150yo are collecting benefits tells me they don't) is the biggest mistake here. I own codebases much smaller than the SSA code and there are still things I don't fully understand about it AND I've caused outages because of it.
Non programmer but skilled with computers type guy here: what makes Java well suited for this?
This is probably an incorrect prejudice of mine, but I always thought those old languages are simpler and thus faster. Didn’t people used to rip on Java for being inefficient and too abstracted?
Last language I had any experience with was C++ in high school programming class in the early 2000s, so I’m very ignorant of anything modern.
-
This post did not contain any content.
The first step towards privatizing an industry is eroding public confidence in the existing program. They have absolutely no intention of improving the program, they just want to make it shitty enough that people stop believing in it. Once that happens, 45 will start shilling, and some lucky company will swoop in and take it over.
Textbook...
-
Jokes aside, nothing wrong with rewriting in Java. It is well-suited for this kind of thing.
Rewriting it in anything without fully understanding the original code (the fact they think 150yo are collecting benefits tells me they don't) is the biggest mistake here. I own codebases much smaller than the SSA code and there are still things I don't fully understand about it AND I've caused outages because of it.
No. Java is not suited for this. This code runs on mainframes not some x86 shitbox cluster of dell blades. They literally could not purchase the hardware needed to switch to java in the timeline given. I get what you're trying to say but in this case Java is a hard no.
-
Ah yes, a classic tale...
"We're going to take this perfectly efficient and functional COBOL code base and rewrite it in Java! And we'll do it in a few months!"
So many more competent people and organizations than them have already tried this and spectacularly crashed and burned. There's are literal case studies on these types of failed endeavors.
I bet they'll do it in Waterfall too.
It's interesting. If they use Grok, this could well be the deathknell for vibe programming (at least for now). It's just fucking traffic that their hubris will cause grief and pain to do many Americans - and cost the lives of more than a few.
It's worth noting that one of those organizations is IBM. Mostly relevant because they're the ones that originally built a lot of that cobol, the mainframes it runs on, and even the compilers that compiled it.
They're basically the people you would expect to be able to do it, and they pretty quickly determined that the cost of a rewrite and handling all the downstream bugs and quirks would exceed the ongoing maintenance cost of just training new cobol developers.My dad was a cobol developer (rather, a pascal developer using a compiler that transpiled to cobol which was then linked with the cobol libraries and recompiled for the mainframe), and before he retired they decided to try to replace everything with c#. Evidently a year later their system still took a week to run the nightly reports and they had rehired his former coworkers at exorbitant contractor rates.
-
This post did not contain any content.
GitHub Copilot about to be clocking some overtime on COBOL conversions.
-
This post did not contain any content.
This idea is terrifying in the most insidious ways. Who has access to the code? Who is auditing the code? Are they putting in code that may disenfranchise "the right people". How long will it take to come to light? When found out, provided 'Adults' are running the country again, how much and how long would it take to fix it?
And what backdoors are in the code?This is bad news all around.
-
Non programmer but skilled with computers type guy here: what makes Java well suited for this?
This is probably an incorrect prejudice of mine, but I always thought those old languages are simpler and thus faster. Didn’t people used to rip on Java for being inefficient and too abstracted?
Last language I had any experience with was C++ in high school programming class in the early 2000s, so I’m very ignorant of anything modern.
Java can be pretty damn efficient for long running processes because it optimizes at runtime. It also can use new hardware features (like cpu instructions) without having to compile for specific platforms so in practice it gets a boost there. Honestly, the worst thing about Java is the weird corporate ecosystem that produces factoryfactory and other overengineered esoteric weirdness. It can also do FFI with anything that can bind via c ABI so if some part of the program needed some hand optimized code like something from BLAS it could be done that way.
All that to say it doesn't matter what language they use anyway, because rewriting from scratch with a short timeline is an insane thing to do that never works.
-
Non programmer but skilled with computers type guy here: what makes Java well suited for this?
This is probably an incorrect prejudice of mine, but I always thought those old languages are simpler and thus faster. Didn’t people used to rip on Java for being inefficient and too abstracted?
Last language I had any experience with was C++ in high school programming class in the early 2000s, so I’m very ignorant of anything modern.
The way Java is practically written, most of the overhead (read: inefficient slowdown) happens on load time, rather than in the middle of execution. The amount of speedup in hardware since the early 2000s has also definitely made programmers less worried about smaller inefficiencies.
Languages like Python or JavaScript have a lot more overhead while they're running, and are less well-suited to running a server that needs to respond quickly, but certainly can do the job well enough, if a bit worse compared to something like Java/C++/Rust. I suspect this is basically what they meant by Java being well-suited.
-
If it fails spectaculairly who will take the blame? Will there be any repercussions at all?
Or will Musk and Trump shrug their shoulders? Halfheartedly blame Biden for badly programming the original database then go play some golf/videogaminges?
I think the hope is that it fails, they don’t want social security to work.
-
Java can be pretty damn efficient for long running processes because it optimizes at runtime. It also can use new hardware features (like cpu instructions) without having to compile for specific platforms so in practice it gets a boost there. Honestly, the worst thing about Java is the weird corporate ecosystem that produces factoryfactory and other overengineered esoteric weirdness. It can also do FFI with anything that can bind via c ABI so if some part of the program needed some hand optimized code like something from BLAS it could be done that way.
All that to say it doesn't matter what language they use anyway, because rewriting from scratch with a short timeline is an insane thing to do that never works.
Why is there a need to rewrite it at all? Is it because COBOL is basically ancient hieroglyphics to modern programmers thus making it hard to maintain or update?
-
This post did not contain any content.
If SS payments stop, there will be hundreds of thousands of people with nothing left to lose.
-
Why is there a need to rewrite it at all? Is it because COBOL is basically ancient hieroglyphics to modern programmers thus making it hard to maintain or update?
I wouldn't necessarily agree it needs to be rewritten. Hiring programmers that are willing to work in cobol would certainly be harder than other languages though, because you'll have a much smaller candidate pool and people would be unlikely to see learning cobol as a good career investment
-
Non programmer but skilled with computers type guy here: what makes Java well suited for this?
This is probably an incorrect prejudice of mine, but I always thought those old languages are simpler and thus faster. Didn’t people used to rip on Java for being inefficient and too abstracted?
Last language I had any experience with was C++ in high school programming class in the early 2000s, so I’m very ignorant of anything modern.
I am a programmer but I'm not sure why people think Java is suited for anything, especially a system so sensitive to bugs. It's so hard to write high quality readable code in Java. Everything is way more clunky, and verbose than it needs to be.
Some major improvements were made with versions 17+ but still, it feels like walking through mud.
It's a language from the 1990s for the 1990s.
Btw the performance is actually pretty good in Java, the old reputation for slowness is entirely undeserved today.
-
GitHub Copilot about to be clocking some overtime on COBOL conversions.
You mean Grok, right?
