Elon Musk Rewriting Computer Code Powering Social Security, What Could Possibly Go Wrong
Oh, the website's down? The website's down.
Having already fucked up the Social Security Administration six ways from Sunday with staff cuts and new ID requirements and field office closures, the incels of the ironically named Department of Government Efficiency are reportedly plotting one more big step in their rampage: They are planning to rewrite the SSA’s entire computer codebase in a more modern programming language. And they plan to have this project completed in “a few months.”
Oh guess what, it’s Saturday morning (Gary wrote this post Friday afternoon) and the Social Security website is already down.
It has been a long time since we had a database/computer technology-adjacent job, but we know enough to understand that migrating a huge system with a reported 60 million lines of code is not something that happens that quickly. This is a years-long sort of job, one that will take the efforts of hundreds, if not thousands, of people. It’s a delicate undertaking, and the vampires of DOGE have proven themselves anything but delicate.
Of course, they have also proven that they genuinely don’t give a shit if you wind up sleeping under a railroad trestle after their hacky changes leave you listed as “dead” in Social Security’s databases, so there is one more reason to not trust them if you needed one.
So, we hope you current Social Security recipients enjoyed getting your benefit checks or your benefit direct deposits on time! Hell, we hope you enjoyed getting them, period. Because there is an excellent chance all that is about to be deader than Elon Musk’s soul.
Wired reports on the new plan in a frightening new story with the words “System Collapse” prominently displayed in the title. It all reads as stupid as it sounds. The basic gist is that SSA systems still run on COBOL, a common, business-oriented programming language that has been around since the 1950s. COBOL has lasted this long for a variety of reasons, but a big one is that it still works really well. Programmers at the SSA still actively work with it despite the existence of newer, more modern programming languages for a few reasons, one of which is that it is very robust. So robust, in fact, that quite a few federal government systems still run on it.
The federal government tends to lag way behind in modernizing the technology that bureaucrats use to keep the country running. But as the saying goes, if it ain’t broke, don’t fix it.
And DOGE has already proven that it is unfamiliar with COBOL conventions, as Wired already explained in an earlier story about why, contra Musk’s band of Nazi virgins, there were not actually millions of Social Security checks going out to 150-year-olds.
This is one system you do not want to screw up until you are absolutely, positively sure any replacement system is up and chugging along. The computers at Social Security are paying benefits to 65 million Americans every month. For many of them, this is their only source of income. Fuck it up, and people, especially the elderly, can’t pay rent or buy food. Their existence is already precarious enough.
Yet that is likely to be the result when the weasels of DOGE (we very much appreciate the Wired locution referring to it as “the so-called Department of Government Efficiency,” as it is anything but that) get through here.
How enormous an undertaking is it to move the SSA off of COBOL? Let Wired tell you:
In order to migrate all COBOL code into a more modern language within a few months, DOGE would likely need to employ some form of generative artificial intelligence to help translate the millions of lines of code, sources tell WIRED. “DOGE thinks if they can say they got rid of all the COBOL in months then their way is the right way and we all just suck for not breaking shit,” says the SSA technologist.
Lot of problems with that, starting with the fact that even generative AI code still has to be checked for errors. And if it’s wrong, someone still has to manually fix it. What do you think the chances are that DOGE will thoroughly test any changes made by either humans or a technology capable of about the same level of thought as a blender? We’re not talking about Jarvis from the Iron Man movies, we’re talking about Large Language Models of code trained on other code written by humans that likely contains plenty of its own errors. The possibilities for disaster are infinite.
DOGE would also need to develop tests to ensure the new system’s outputs match the previous one. It would be difficult to resolve all of the possible edge cases over the course of several years, let alone months, adds the SSA technologist.
This is just basic quality assurance testing. But if there’s one thing we’ve learned about the sorts of dweebs hired by Elon Musk — and by Donald Trump for that matter, he’s still allegedly the president — is that they simply shrug when something breaks before moving along to the last thing. Careless people smashing things up and then leaving the mess in their wakes for others to clean up, as F. Scott Fitzgerald once memorably said of another generation of arrogant, over-moneyed chucklefucks.
Wags online are suggesting that breaking Social Security is the entire point. Conservatives have long wanted to end the program. But too many people rely on it, so cuts are impossible to get through Congress. It’s the infamous third rail of American politics.
If, on the other hand, Social Security broke because a bunch of nerds broke it, and then nobody could get hold of anyone at the agency to help sort out why their measly $2,000 check hasn’t come through this month because DOGE shut down all phone help lines and closed many field offices that people could otherwise have gone to, well, that’s just an act of God that can’t be helped. Shrug and move on to the next thing, the Silicon Valley ethos.
We doubt it is one reason more than another. Sure, ending Social Security through the back door would fulfill a long-term goal of the Right. It could also be that the DOGE guys really are so high on themselves that they look at government programmers and think, What a bunch of dinosaurs! Get out of the way, old people, and let us show you how this shit gets done.
Well, we weren’t going to be able to retire for awhile anyway. Now maybe we’ll just work until we drop dead under that railroad trestle where we’ll spend our dotage.
[Wired]
Wonkette is reader-supported and busily stockpiling canned goods for our old age.
"project completed in “a few months.”
laughs in retired IT consultant
My career was in I.T. and coding, starting with COBOL, later C, C++, and C#. Annual goals always included rewriting older applications in a newer language. Not because the newer language was intrinsically better but to cross the older language off the needed skills for developers.
Almost none of those rewrites ever took place. Why? The old application was, by virtue of begin old, very stable; rewrites introduced bugs and required extensive acceptance testing which the business areas were unwilling to provide for such a small (to them) ROI.