DOGE Plans to Rebuild SSA Codebase in Months, Risking Benefits and System Collapse
-
GitHub Copilot about to be clocking some overtime on COBOL conversions.
You mean Grok, right?
-
I think the hope is that it fails, they don’t want social security to work.
"Whoops, we pushed to prod and have no backups. Sorrryyyy!"
-
This post did not contain any content.
This is how you know Musk is a fraud. This far into his career and he’s leading teams into rookie mistakes.
Or, he knows this will break it and that’s the goal. I’m just not sure how he avoids the blame.
-
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.
How many bugs? How will they secretly siphon money to their accounts? How much access will the Russians have? Who's gonna get discriminated against?
-
If SS payments stop, there will be hundreds of thousands of people with nothing left to lose.
Over 70 million including many retirees, orphans, and disabled workers. The people most in need of help and the reason that trying to run a government like a capitalist business is one of the dumbest forms of government organization ever. A quick way to radicalize someone against you is to harm their family or take their money.
-
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”
My company actually wrote their flagship software in COBOL starting in the 80s, and we're only now six years into rewriting everything in a more modern language with probably four years to go.
I can't imagine trying to start such a project like rewriting all of Social Security and thinking it will take months. You have to be a special kind of fatuous to unironically think that.
-
My company actually wrote their flagship software in COBOL starting in the 80s, and we're only now six years into rewriting everything in a more modern language with probably four years to go.
I can't imagine trying to start such a project like rewriting all of Social Security and thinking it will take months. You have to be a special kind of fatuous to unironically think that.
I was briefly employed at a firm that maintained the sales commission software for a large telecom firm.
It was 1.5 million lines of VB6, though VB8 was already three years old. Nobody knew all of it, so they couldn’t possibly rewrite it to handle all the edge cases and special incentives we kept having to add.
Except maybe the lone QA person, who would frequently begin sobbing at her desk. And we could all hear it because it was an open plan office and we weren’t allowed to wear headphones.
That job was so bad I quit and began freelancing.
-
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
COBOL is the career advise you hear people give for people who want to make money but don't want to deal with the VC clownshow. COBOL btw is only 13 years older than C and both language's current standard dates to 2023.
It's at its core a bog-standard procedural language, with some special builtins making it particularly suited to do mainframe stuff. Learning COBOL is no worse a career investment than learning ABAP, or any other language of the bureaucracy. Sure you'll be a career bureaucrat but that's up sufficiently many people's alley, no "move fast and break things", it's "move slowly and keep things running".
-
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...
Yep, this is it. Show how “broken” it is by breaking it, and enough of the population won’t even notice when it’s “fixed” and they’re only getting 2/3 of what they were before (and are entitled to). Plus grift, etc.
-
COBOL is the career advise you hear people give for people who want to make money but don't want to deal with the VC clownshow. COBOL btw is only 13 years older than C and both language's current standard dates to 2023.
It's at its core a bog-standard procedural language, with some special builtins making it particularly suited to do mainframe stuff. Learning COBOL is no worse a career investment than learning ABAP, or any other language of the bureaucracy. Sure you'll be a career bureaucrat but that's up sufficiently many people's alley, no "move fast and break things", it's "move slowly and keep things running".
Everything that you said is correct, except the prevalence of the career advice. I would bet most people looking for their first job out of school don't even know COBOL is a language.
-
COBOL is the career advise you hear people give for people who want to make money but don't want to deal with the VC clownshow. COBOL btw is only 13 years older than C and both language's current standard dates to 2023.
It's at its core a bog-standard procedural language, with some special builtins making it particularly suited to do mainframe stuff. Learning COBOL is no worse a career investment than learning ABAP, or any other language of the bureaucracy. Sure you'll be a career bureaucrat but that's up sufficiently many people's alley, no "move fast and break things", it's "move slowly and keep things running".
The language isn't the problem with COBOL, it's the likelihood that you will be maintaining (not adding to, but maintaining) a software system that may not have any docs and the original implementers are dead. Next, there will be nobody to verify the business rules that are specified in the code. Finally after you make a mistake about a business rule, you will be thrown under the bus.
-
My company actually wrote their flagship software in COBOL starting in the 80s, and we're only now six years into rewriting everything in a more modern language with probably four years to go.
I can't imagine trying to start such a project like rewriting all of Social Security and thinking it will take months. You have to be a special kind of fatuous to unironically think that.
The kind that thinks full self driving is two years away, perhaps?
-
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.
Other than hardware issues, which someone else mentioned, it has a lot of enterprise-grade functionality that make it more secure and auditable than a lot of other languages. And despite, or maybe because of, its large memory footprint it's actually faster than most languages.
I totally get any hate about writing Java though. It is a verbose language. Using Kotlin instead helps with that.
-
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.
What's "vibe programming"?
-
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?
Refactoring a code base is kinda like general maintenance for the application. Over time deprecated features, temp fixes, etc. start to be a lot of the code base. By cleaning things up you can make it more maintainable, efficient, etc.
That being said, for systems this large you usually fix up parts of it and iterate over time. Trying to do the whole code base is hard cause it's like replacing the engine while the car is in motion.
-
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?
They want to make buttloads of money from a rewrite, and it would cost buttloads to do this. They probably also want things to run like shit and cause misery for retired Americans.
-
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.
It's a verbose language but I don't know if there's any real language that encourages highly readable code beyond low-level syntax. You want to create a God-class in Python with nonsensical variables and 5 levels of nesting? The language won't stop you.
-
What's "vibe programming"?
Stupid term for when people who don't know how to program ask AI to generate code for them which they have no expertise to actually validate.
-
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.
Uh, Java is specifically supported by IBM in the Power and Z ISA, and they have both their own distribution, and guides for writing Java programs for mainframes in particular.
This shouldn't be a surprise, because after Cobol, Java is the most enterprise language that has ever enterprised.
-
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.
screams in quality assurance
