Take heart Democrats... Even a single month's interruption in social security benefits will swing tens of millions of votes immediately.

You think the government hasn't ever fucked up someone's social security payment?
Oh sure.....not on a mass scale though...
They need to go right ahead with it but carefully.
It's the single largest voting block in the nation and it is Very sensitive. Can't fumble the football with this one.
 
Oh sure.....not on a mass scale though...
They need to go right ahead with it but carefully.
It's the single largest voting block in the nation and it is Very sensitive. Can't fumble the football with this one.
"They need to go right ahead with it but carefully."

Everything Trump does is hastily patched together and mismanaged.

Doing things methodically and carefully is not the way he conducts business.
 
"They need to go right ahead with it but carefully."

Everything Trump does is hastily patched together and mismanaged.

Doing things methodically and carefully is not the way he conducts business.

Well he better be careful with this one.
I'm not speaking from personal experience since my own financial circumstances are very solid and do not depend on the government.

However I know many people who would sink into a financial abyss for missing even one month's benefits. People that didn't plan while I suppose.

There are a lot of them .. probably the largest voting block in the nation.

Make them miss one payment and you immediately create a massive solidarity that will swing to the other side instantaneously with pretty much no recourse or reverse.
 
There will be no disruption in social security checks.
You're probably right.... However if they do somehow manage to overload the system and it burps the consequences will be enormous.
 
This has nothing to do with education or belief in anything. This is the one single hot button issue that cannot be negotiated with. People who Miss even a single payment will be completely convinced and extremely difficult to de-convince if not impossible. The much smarter approach to this would be to slowly but surely begin upgrading the entire system to a modern software. Make the corrections slowly over the course of the next two to three years. If they fumble this football they fumble the whole game.

Just FYI, being in information systems myself.

Please don't take this post as any attempt to be rude, it's not.

But the thought that the SSA core infrastructure of 1960's era COBOL mainframes can be replaced in 2-3 years isn't realistic. It would take probably a couple of billion dollars over the course of a decade to replace. Verizon has the contract up upgrade and modernize the FAA system and this multiple billions of dollars over the course of 15 years. (Actually I think the couple of Billion is just the starting phase.)

  • First you have to define what the critical infrastructure is supposed to look like in terms of size, scope, locations, and network from a Technology standpoint. Then you have to define the size, scope, record volumn, and functionality from a software standpoint. That would take the SSA a year or two.
  • Then you have to put it out for RFP (Request for Proposal) to vendors and the big players in that field are Oracle, SAS, and Microsoft. And this can take multiple rounds as vendors will have questions that need answer before they can cost it out. This could take another year or two.
  • You have to get Congress onboard to - you know - actually fund the project in the budget. Who knows how long that would take.
  • Once the vendor is selected and and actual design work can start, now you have to build a database system from the ground up that meets the operational requirements in terms of functionality and scope but that also provides for historical tracking, record maintenance, determination of benefits, and payment of those benefits in such a manner as to comply with existing laws and regulations. That alone would take a couple of years.
  • Because this is critical infrastructure you are going to have to go through various testing phases:
    • Functional Testing of subsystems to check performance and compliance.
    • Beta Testing of the entire system for all planned scenarios
    • Alpha Testing under real world conditions to see if performs properly and is in compliance now that real situations are being tested.
    • Parallels Testing - As critical infrastructure you would never, NEVER just turn off the old system and turn on the new system. You would run the old system for actual production and then run the same processing through the new system in a "Safe" environment to identify issues for correction. Here alone it would probably be recommended that parallels run for at least one entire tax year.
  • Oh and don't forget you don't get to start with a clean, empty system. You have to be able to convert and correct existing data in the COBOL system to this new infrastructure.
  • Finally, you then get to "Go Live" with the new system.

This is critical infrastructure and CANNOT FAIL, so it has to be designed with care, constructed comply with laws and regulation, and be tested properly.

This is NOT Rocket Science. In rocket science is an interrative process, you design, you build, you launch, and you gather data about what went wrong. You repeat the process over and over again - build, test to failure, build test to failure. That can't happen with such things as replacement FAA and SSA systems.

This isn't ordering a DELL desktop.

Just my thoughts.

WW
 
Just FYI, being in information systems myself.

Please don't take this post as any attempt to be rude, it's not.

But the thought that the SSA core infrastructure of 1960's era COBOL mainframes can be replaced in 2-3 years isn't realistic. It would take probably a couple of billion dollars over the course of a decade to replace. Verizon has the contract up upgrade and modernize the FAA system and this multiple billions of dollars over the course of 15 years. (Actually I think the couple of Billion is just the starting phase.)

  • First you have to define what the critical infrastructure is supposed to look like in terms of size, scope, locations, and network from a Technology standpoint. Then you have to define the size, scope, record volumn, and functionality from a software standpoint. That would take the SSA a year or two.
  • Then you have to put it out for RFP (Request for Proposal) to vendors and the big players in that field are Oracle, SAS, and Microsoft. And this can take multiple rounds as vendors will have questions that need answer before they can cost it out. This could take another year or two.
  • You have to get Congress onboard to - you know - actually fund the project in the budget. Who knows how long that would take.
  • Once the vendor is selected and and actual design work can start, now you have to build a database system from the ground up that meets the operational requirements in terms of functionality and scope but that also provides for historical tracking, record maintenance, determination of benefits, and payment of those benefits in such a manner as to comply with existing laws and regulations. That alone would take a couple of years.
  • Because this is critical infrastructure you are going to have to go through various testing phases:
    • Functional Testing of subsystems to check performance and compliance.
    • Beta Testing of the entire system for all planned scenarios
    • Alpha Testing under real world conditions to see if performs properly and is in compliance now that real situations are being tested.
    • Parallels Testing - As critical infrastructure you would never, NEVER just turn off the old system and turn on the new system. You would run the old system for actual production and then run the same processing through the new system in a "Safe" environment to identify issues for correction. Here alone it would probably be recommended that parallels run for at least one entire tax year.
  • Oh and don't forget you don't get to start with a clean, empty system. You have to be able to convert and correct existing data in the COBOL system to this new infrastructure.
  • Finally, you then get to "Go Live" with the new system.

This is critical infrastructure and CANNOT FAIL, so it has to be designed with care, constructed comply with laws and regulation, and be tested properly.

This is NOT Rocket Science. In rocket science is an interrative process, you design, you build, you launch, and you gather data about what went wrong. You repeat the process over and over again - build, test to failure, build test to failure. That can't happen with such things as replacement FAA and SSA systems.

This isn't ordering a DELL desktop.

Just my thoughts.

WW
Excellent post....

Yes I thought it might be that difficult. I wasn't sure but I did have some experience with GE genius block upgrades to Turbine control machinery. It was Grueling and we had to look high and low and pull a few people out of retirement to make the transition which took months. During the transition there were many failures. Eventually it was done.

I can't even imagine the amount of work and concentration it would take to make such a transition where failure is not an option. We actually counted on the failures to create a break in the mind busting work of translating antiquated information systems line by line to the new system.

I didn't take your post as rude at all. It was very informational, well presented and quite believable.
 
Last edited:
Well he better be careful with this one.
I'm not speaking from personal experience since my own financial circumstances are very solid and do not depend on the government.

However I know many people who would sink into a financial abyss for missing even one month's benefits. People that didn't plan while I suppose.

There are a lot of them .. probably the largest voting block in the nation.

Make them miss one payment and you immediately create a massive solidarity that will swing to the other side instantaneously with pretty much no recourse or reverse.
The likelihood of that happening is like you getting your third set of teeth! Of course, you probably are a genetic disaster looking at your avatar. Is that a selfie? :p
 
The likelihood of that happening is like you getting your third set of teeth! Of course, you probably are a genetic disaster looking at your avatar. Is that a selfie? :p
Pretty close...lol...and man....I would Love a third set of teeth! The first thing I would do is go find a nice Baldwin Apple and spend the next 20 minutes in heaven.
 
Why would anyone want to eat a hairy apple? Most people would prefer a bald one!
Well I already have the Bald! But you ain't lived till you picked one of these babies right off the tree.

Need those third teeth! Prontocaciously!
Screenshot_20250310-194600.webp
 
The current acting administrator of the social security administration has indicated that he believes the DOGE team is bound to make mistakes in their effort to examine social security and its payment system. He admits that it needs to be done but considering the fact that it runs on a 65-year-old poorly maintained and antiquated piece of software he is certain that the software engineers working for Musk will fumble through it and cause it to malfunction almost definitely.

I have to emphasize that while I support this effort It must be observed and noted that even a single mistake that interrupts benefits only once..... Will be the single most powerful trigger to vote flipping anyone has ever seen.
It will happen quickly and have lasting damage.

This should be interesting to watch.

Jo
481078064_635281325780910_5823668051311382338_n.webp
480454178_648708721260225_4903768144513059520_n.webp
481915225_122171613056279179_8930408862160437455_n.webp
 
Just FYI, being in information systems myself.

Please don't take this post as any attempt to be rude, it's not.

But the thought that the SSA core infrastructure of 1960's era COBOL mainframes can be replaced in 2-3 years isn't realistic. It would take probably a couple of billion dollars over the course of a decade to replace. Verizon has the contract up upgrade and modernize the FAA system and this multiple billions of dollars over the course of 15 years. (Actually I think the couple of Billion is just the starting phase.)

  • First you have to define what the critical infrastructure is supposed to look like in terms of size, scope, locations, and network from a Technology standpoint. Then you have to define the size, scope, record volume, and functionality from a software standpoint. That would take the SSA a year or two.
  • Then you have to put it out for RFP (Request for Proposal) to vendors and the big players in that field are Oracle, SAS, and Microsoft. And this can take multiple rounds as vendors will have questions that need answer before they can cost it out. This could take another year or two.
  • You have to get Congress onboard to - you know - actually fund the project in the budget. Who knows how long that would take.
  • Once the vendor is selected and and actual design work can start, now you have to build a database system from the ground up that meets the operational requirements in terms of functionality and scope but that also provides for historical tracking, record maintenance, determination of benefits, and payment of those benefits in such a manner as to comply with existing laws and regulations. That alone would take a couple of years.
  • Because this is critical infrastructure you are going to have to go through various testing phases:
    • Functional Testing of subsystems to check performance and compliance.
    • Beta Testing of the entire system for all planned scenarios
    • Alpha Testing under real world conditions to see if performs properly and is in compliance now that real situations are being tested.
    • Parallels Testing - As critical infrastructure you would never, NEVER just turn off the old system and turn on the new system. You would run the old system for actual production and then run the same processing through the new system in a "Safe" environment to identify issues for correction. Here alone it would probably be recommended that parallels run for at least one entire tax year.
  • Oh and don't forget you don't get to start with a clean, empty system. You have to be able to convert and correct existing data in the COBOL system to this new infrastructure.
  • Finally, you then get to "Go Live" with the new system.

This is critical infrastructure and CANNOT FAIL, so it has to be designed with care, constructed comply with laws and regulation, and be tested properly.

This is NOT Rocket Science. In rocket science is an interactive process, you design, you build, you launch, and you gather data about what went wrong. You repeat the process over and over again - build, test to failure, build test to failure. That can't happen with such things as replacement FAA and SSA systems. This isn't ordering a DELL desktop. Just my thoughts. WW
1. The SS programming shouldn't be too sophisticated
2. Google engineers redesigned Obama's "train wreck" rollout of Obamacare in 2-weeks.
3. The bigger challenge will be getting the "paper only" pension system stored in that PA mine converted to computers, ugh.
 
Back
Top Bottom