This thing has become such an epic bucket of FAIL I thought it deserved its own thread.
For those of you who haven't followed this debacle, let me bring you up to speed:
You have a $500 million dollar+ website written in part by a foreign company (while to be fair they've done similar work for the "Romneycare" website, are we so lacking in capability that our country has to outsource this task to any foreign company?) which has more or less failed to work from Day One.
Now we have things like this:
http://m.weeklystandard.com/blogs/o...ement-copyrighted-software_763666.html?morans
Or this:
http://www.washingtonpost.com/blogs/wonkblog/wp/2013/10/14/five-thoughts-on-the-obamacare-disaster/
This:
http://www.californiahealthline.org...structural-problems-caused-aca-website-issues
And you wanted to register?
http://arstechnica.com/information-...-button-on-passwords-as-contractors-scramble/
Whatever your opinion of the law and all surrounding it, we've spent a half-a-billion dollars on something that doesn't work, wasn't properly tested, and has at least one copyright violation (albeit minor, it speaks volumes about the abilities of the programmers and their QA department).
Nicely done. Everyone take a bow.
For those of you who haven't followed this debacle, let me bring you up to speed:
You have a $500 million dollar+ website written in part by a foreign company (while to be fair they've done similar work for the "Romneycare" website, are we so lacking in capability that our country has to outsource this task to any foreign company?) which has more or less failed to work from Day One.
Now we have things like this:
http://m.weeklystandard.com/blogs/o...ement-copyrighted-software_763666.html?morans
The latest indication of the haphazard way in which Healthcare.gov was developed is the uncredited use of a copyrighted web script for a data function used by the site, a violation of the licensing agreement for the software.
Or this:
http://www.washingtonpost.com/blogs/wonkblog/wp/2013/10/14/five-thoughts-on-the-obamacare-disaster/
The backroom connection between the insurance companies and the federal government is a disaster. Things are worse behind the curtain than in front of it"
Here is one example from a carrier–and I have received numerous reports from many other carriers with exactly the same problem. One carrier exec told me that yesterday they got 7 transactions for 1 person – 4 enrollments and 3 cancellations.
For some reason the system is enrolling, unenrolling, enrolling again, and so forth the same person. This has been going on for a few days for many of the enrollments being sent to the health plans. It has got on to the point that the health plans worry some of these very few enrollments really don’t exist.
This:
http://www.californiahealthline.org...structural-problems-caused-aca-website-issues
In addition, some users who already had established accounts could not access them. Others were asked to verify their email addresses to gain access to their accounts, but the verification link did not work as intended, the Times reports.
Park said that exchange officials now have a clear understanding of the issues, adding that "contractors have sent reinforcements" and are "working 24-7" to rectify the issues. He suggested that high traffic also was a likely factor for the problems. Park said, "At lower volumes, [the software] would work fine," but "[a]t higher volumes, it has problems."
And you wanted to register?
http://arstechnica.com/information-...-button-on-passwords-as-contractors-scramble/
Amid all the attention, bugs, and work happening at Healthcare.gov in light of the Affordable Care Act, potential registrants talking to phone support today have been told that all user passwords are being reset to help address the site's login woes. And the tech supports behind Healthcare.gov will be asking more users to act in the name of fixing the site, too. According to registrants speaking with Ars, individuals whose logins never made it to the site's database will have to re-register using a different username, as their previously chosen names are now stuck in authentication limbo.
Whatever your opinion of the law and all surrounding it, we've spent a half-a-billion dollars on something that doesn't work, wasn't properly tested, and has at least one copyright violation (albeit minor, it speaks volumes about the abilities of the programmers and their QA department).
Nicely done. Everyone take a bow.