Brandon wrote: Since you've previously repeated that the quality of the code was good enough for government work, I conclude from your post above that the problem was poor capacity planning.
Again, it's 'bagger logic...ACA is a failure because so many people want to use it.
It is not my problem if you are non-skilled in Information Technologies. And it doesn't appear that you have reached out to the numerous on line articles and information from the tech community discussing the issue.
The bottom line is not capacity (although capacity issues is the first thing end users encounter). You could increase capacity (which is done with hardware) and you would be seeing a lot of the same results.
I'll put it in laymen terms for you. A toll stop on a highway only has one lane, so they build 5 more toll lanes (that's capacity). But the highway after the toll booths is still one lane (that's the software). You can do all the loading improvements you want, but if the code (the highway) that takes you to where you want to get to is broken, ya can't get ther' from here.
The other night they had to DELETE all the users password (from the users that managed to get that far).
A simple real world example.
"All passwords were deleted for existing accounts as part of the upgrade process," a call center representative told CNN's Elizabeth Cohen. The representative said users experiencing issues must call in to reset their password; it cannot be done online.
http://www.wptv.com/dpp/news/science_te ... an-upgrade
That's a software issue partner. That's a database issue Gomer. If a software routine written to collect, post and retrieve passwords and user names can't be reused with ANY changes that they made, then that routine itself is defective and badly written. (look up black box, objects, properties, functions, inheritance).
Evidently they started rebuilding some portion of the system from scratch if they had to go as far as deleting all existing passwords.
Any programmer of any experience can write an object that collects, post and retrieves passwords in about an hour. And that includes checking for existing passwords, duplicate user names, encrypting the data and any other design restrictions that the programmer has to deal with.
And that object would be usable with ANY infrastructure that needed to use that object. In the old days we called that "black boxing."
If they had to delete all passwords then what ever was putting those passwords away to the database was defective.
I don't mind explaining all this, I wish the public was better educated in Information Technologies and what goes on behind the toys they hold in their hands.
Again it's "government-expanding ecoweenie" logic to hide from the facts.
Maybe you would like to explain how the major problem was only capacity since you're so locked into that Obama administration excuse?
P.S
Brandon wrote: There are unemployed computer programmers looking for work.
I've been a employed computer programmer since 1978 and spent 15 years working as a programmer for the Federal government.
You aren't exactly brimming with sources either are you? All you have is a pleading promise that it will get better. Sort of like Obama's pleading promises that unemployment will get better. Brandon, how long should we expect to wait? It has been five years of horrible unemployment numbers and we are still at 7%. Even though less adults have been working than since the late 1970's.
