Healthcare.gov crashing because backend doomed in the requirements stage
1–10 of 57 posts
Re: Healthcare.gov crashing because backend doomed in the requirements stage
#2I can't wait to see what the report of it didn't work actually says. It's quite possible that one of the services that the website hit couldn't handle the traffic which in turn caused a bottleneck in other systems.
Re: Healthcare.gov crashing because backend doomed in the requirements stage
#3I know the people who worked on this. This is not what happened. Just yet another propaganda piece by Forbes.
Re: Healthcare.gov crashing because backend doomed in the requirements stage
#4I know the people who worked on this. This is not what happened. Just yet another propaganda piece by Forbes.
Can you elaborate on what did happen?
Re: Healthcare.gov crashing because backend doomed in the requirements stage
#5Thoughtback [https://thoughtback.com/] sent me a pertinent reminder this morning. No affiliation, just a great tool.
Organizational metrics, which are not related to the code, can predict software
failure-proneness with a precision and recall of 85 percent. This is a significantly
higher precision than traditional metrics such as churn, complexity, or coverage
that have been used until now to predict failure-proneness. [1]
[1] The Influence of Organizational Structure On Software Quality: An Empirical Case Studyhttp://research.microsoft.com/apps/pubs/default.aspx?id=7053...
--
edit: formatting
Re: Healthcare.gov crashing because backend doomed in the requirements stage
#6I know the people who worked on this. This is not what happened. Just yet another propaganda piece by Forbes.
Well something happened. You might want to tell those guys that 500 million lines of code is a bit ridiculous.
Re: Healthcare.gov crashing because backend doomed in the requirements stage
#7Could anyone share which platform / framework they used?
Re: Healthcare.gov crashing because backend doomed in the requirements stage
#8I know the people who worked on this. This is not what happened. Just yet another propaganda piece by Forbes.
> the interface kept asking me to reenter the information for our dependents. Farther on in the process it doubled the number of our children (to 6!) Even though it listed our children’s names twice (identically) and even though these clones had identical SS numbers, the validation software was not smart enough to realize that the duplicate records were describing the same people!
This didn't happen? Are you suggesting he made this whole story up?
Re: Healthcare.gov crashing because backend doomed in the requirements stage
#9Re: Healthcare.gov crashing because backend doomed in the requirements stage
#10> In my case, even the most expensive plan for our family in the State of Maine, where we live, is half the cost of what we are currently paying, exclusive of any subsidies.
The elephant in the room is that this is not the typical case - http://www.forbes.com/sites/theapothecary/2013/09/25/double-...