working on
agovernment software
FTFY
Comment on How does this pic show that Elon Musk doesnt know SQL?
darkmarx@lemmy.world 5 days ago
“The government” is multiple agencies and departments. There is no single computer system, database, mainframe, or file store that the entire US goverment uses. There is no standard programming language used. There is no standard server configuration. Each agency is different. Each software project is different.
When someone says the government doesn’t use sql, they don’t know what they are talking about. It could be refering to the fact that many government systems are ancient mainframe applications that store everything in vsam. But it is patently false that the government doesn’t use sql. I’ve been on a number of government contracts over the years, spanning multiple agencies. MsSQL was used in all but one.
Furthermore, some people share SSNs, they are not unique. It’s a common misconception that they are, but anyone working on a government software learns this pretty quickly. The fact that it seems to be a big shock goes to show that he doesn’t know what he is doing and neither do the people reporting to him.
Not only is he failing to understand the technology, he is failing to understand the underlying data he is looking at.
corsicanguppy@lemmy.ca 5 days ago
DahGangalang@infosec.pub 5 days ago
Yeah, obviously ol’ boy is tripping if he thinks SQL isn’t used in the government.
Big thing I’m prying at is whether there would be a legitimate purpose to have duplicated SSNs in the database (thus showing the Vice Bro doesn’t understand how SQL works).
I’m not aware of any instance where two people share an SSN though. The Social Security Administration even goes as far as to say they don’t recycle the SSNs of dead people (its linked a couple times in other comments and Voyager doesn’t let me save drafts of comments, I’ll make an edit to this comment with that link for you).
Can you point me to somewhere showing multiple people can share an SSN?
ryegye24@midwest.social 5 days ago
Assuming the whole “duplicate SSN” thing isn’t just a complete fabrication, we have no idea what table he was even looking at! A table of transactions e.g. would have a huge number of duplicate SSNs.
homicidalrobot@lemm.ee 5 days ago
The fact that SSN aren’t singular identifiers has been public knowledge for quite a while. ID analytics has shown in over a decade of studies that some people have multiple SSN attached to their name, while some (over five million) SSN are used by three or more living individuals. If you search “ID analytics SSN” you’ll find loads of articles reporting on this dating back to 2010 and a bit before.
DahGangalang@infosec.pub 4 days ago
Was trying to find something from the SSA itself on the topic, but didn’t turn anything useful up on the quick.
Here is a link for the lazy on the topic: https://www.nbcnews.com/technolog/odds-someone-else-has-your-ssn-one-7-6C10406347
WarlordSdocy@lemmy.world 5 days ago
I mean I don’t know a ton about SQL but one thing to keep in mind about SSNs is they were not originally meant to be used for identification but because we have no form of national id and places still needed a way to verify who you are people just started using SSNs for that since it’s something everyone has and there wasn’t really a better option. So now the government has been having to try and make them work for that and make them more secure. The better solution would be to make some form of national id that is designed to be secure but Republicans and people like Musk would probably call that government overreach or a way to spy and track people.
DahGangalang@infosec.pub 4 days ago
Ugh, YES, I am so frustrated at the counter arguments for this that I constantly hear spouted by my (ultra-conservative) family.
I hope that notion re-enters the public consciousness as a part of this (not holding my breath tho)
socsa@piefed.social 5 days ago
My wife has a tax payment history under two different legal names which share a single SSN
DahGangalang@infosec.pub 4 days ago
Hmmm, well I can’t speak to how the actual databases are put together, so maybe they would have that as two separate unique primary keys with a duplicated SSN.
But it really seems like bad design if they out it together that way…
JoeyJoeJoeJr@lemmy.ml 4 days ago
Worth noting is that “good” database design evolved over time (en.wikipedia.org/wiki/Database_normalization). If anything was setup pre-1970s, they wouldn’t have even had the conception of the normal forms used to cut down on data duplication. And even after they were defined, it would have been quite a while before the concepts trickled down from acedmemia to the engineers actually setting up the databases in production.
On top of that, name to SSN is a many-to-many relationship - a single person can legally change their name, and may have to apply for a new SSN (e.g. in the case of identity theft). So even in a well normalized database, when you query the data in a “useful” form (e.g. results include name and SSN), it’s probably going to appear as if there are multiple people using the same SSN, as well as multiple SSNs assigned to the same person.
Tarquinn2049@lemmy.world 5 days ago
This is from 15 years ago, so I don’t know how much has changed since then. But this sounds like the sort of thing they mean.
nbcnews.com/…/odds-someone-else-has-your-ssn-one-…
DahGangalang@infosec.pub 4 days ago
In responding to other comments, I’ve found similar things.
All the same, thanks for the resources!
kboy101222@sh.itjust.works 5 days ago
I’d imagine the numbers of dead people eventually get cycled around to. 9 digits only gives you 999,999,999 people to go through, and we have over a third of that in existence right now.