I write software for a living.
Something that has 5 million lines of code would take years JUST TO FIGURE OUT what it is doing, before you can fix it.
Is there documentation?
You can’t just throw more programmers at it, and they will look and say “aha! here’s your problem~!” and add a few more lines of code that fixes it..
First they have to understand what it is doing before they can fix it. This often takes longer then it took to originally write the software.
Like other multi-million dollar software disasters from the government, this will HAVE TO BE SCRAPPED. It would be cheaper to re-write it than to try to fix it.
It is like building a house. If the foundation is bad, the whole house will fall down. But if you throw more builders on the project and they add another bathroom and a new roof , it is still on a bad foundation.
it’s axiomatic that the first thing you do get a non performing software program on track is to cut the number of programmers, not increase them.
So, and I’m going out on a limb here, you’re thinking the crack Verizon emergency software repair team may not be able to save Obamaware?