• Security incident: ISF was recently accessed by intruders. Please change your password, and change it anywhere else you used it. Read more

Heeeeeeere's Obamacare!

Here is what's going on in one line of code:

ODS++

If that's what it takes to make you feel better about it, have at it. But the fact remains that the site is a steaming turd, and still malfunctioning weeks after rollout.
 
If that's what it takes to make you feel better about it, have at it. But the fact remains that the site is a steaming turd, and still malfunctioning weeks after rollout.

Meh. It'll get fixed and people like me are about to get better coverage.
 
Here is what's going on in one line of code:

ODS++

I see what you did there! It's almost like code. Very cute. And it reflects nicely that this "ODS" you speak of (where people are holding the Obama administration responsible for this steaming turd of a website rather than the users, browsers, critics, or system of free enterprise) is indeed incrementing, most likely every time someone tries to sign up.
 
In the context of a message forum, it's understandable that certainty is not reachable when evidence requires divulging personal information. A better question is what details that are reasonable to post would be the most useful in evaluation?
 
In the context of a message forum, it's understandable that certainty is not reachable when evidence requires divulging personal information. A better question is what details that are reasonable to post would be the most useful in evaluation?

Name of the carrier, the location and income level would help. The name of the specific plan within the carrier will also be useful.
 
The latest poop from the New York Times:

Contractors See Weeks of Work on Health Site

Federal contractors have identified most of the main problems crippling President Obama’s online health insurance marketplace, but the administration has been slow to issue orders for fixing those flaws, and some contractors worry that the system may be weeks away from operating smoothly, people close to the project say.

Indeed, several said, the login problems, though vexing to consumers, may be the easiest to solve. One specialist said that as many as five million lines of software code may need to be rewritten before the Web site runs properly.

Senator Marco Rubio, Republican of Florida, said on “Fox News Sunday” that the early failures do not bode well for the rest of the health care law, adding: “In the 21st century, setting up a Web site where people can go on and buy something is not that complicated.”

One major problem slowing repairs, people close to the program say, is that the Centers for Medicare and Medicaid Services, the federal agency in charge of the exchange, is responsible for making sure that the separately designed databases and pieces of software from 55 contractors work together. It is not common for a federal agency to assume that role, and numerous people involved in the project said the agency did not have the expertise to do the job and did not fully understand what it entailed.

“The issue right now is between C.M.S. and the White House,” a specialist said Friday before communications improved. “Everybody sits and waits and the meter runs.”

Insurers have found that the system provides them with incorrect information about some enrollees, repeatedly enrolls and cancels the enrollments of others, and simply loses the enrollments of still others.

According to one specialist, the Web site contains about 500 million lines of software code. By comparison, a large bank’s computer system is typically about one-fifth that size.
 
What... in the.. .err... :rule10 :confused::confused:

500 MILLION lines of code?

Well, at least the tax payers got a decent deal: we got over 1 line of code for each dollar for the website.

I'm guessing that includes all the databases and other software used on the back end? The article states:
One major problem slowing repairs, people close to the program say, is that the Centers for Medicare and Medicaid Services, the federal agency in charge of the exchange, is responsible for making sure that the separately designed databases and pieces of software from 55 contractors work together. It is not common for a federal agency to assume that role, and numerous people involved in the project said the agency did not have the expertise to do the job and did not fully understand what it entailed.
 
I'm guessing that includes all the databases and other software used on the back end? The article states:
55 cooks making the stew... I can't see how that could go wrong!

I guess there were a lot of campaign donors and insiders and cronies who had to get a piece of the pie.
 
Anyway, however many lines of code are involved isn't really the important question. What matters is, does it work?

One more thing from the NYT article:
In the last 10 months alone, government documents show, officials modified hardware and software requirements for the exchange seven times. It went live on Oct. 1 before the government and contractors had fully tested the complete system. Delays by the government in issuing specifications for the system reduced the time available for testing.
I'm no expert in this, but it seems unfair, perhaps, to blame the contractors if the goalposts keep getting moved like that. Although it doesn't say if these changes in requirements were major changes or minor tweaks.
 
Anyway, however many lines of code are involved isn't really the important question. What matters is, does it work?

One more thing from the NYT article:

I'm no expert in this, but it seems unfair, perhaps, to blame the contractors if the goalposts keep getting moved like that. Although it doesn't say if these changes in requirements were major changes or minor tweaks.

Changes in software are par for the course. There's even a name for this hot new strategy called agile development. Lack of testing is bad, however. I'm just questioning all this breathless reporting. The site will get fixed soon enough.
 
"Lines of code" is kind of a useless statistic, it doesn't tell you anything substantial about the system.

It sounds impressive, though.
 
Did anyone actually bother asking the president at his press conference why this company won the contract despite its spotty performance record?

Or were the sycophants too busy admiring the crease in his pants and getting tingles up their leg and crap.
 
I think it's awesome how the GOP has been forced to shift gears from attacking the concept to attacking the implementation, personally. It really shows just how little ammunition they had to attack the concept in the first place, and has forced them to admit that while there are indeed flaws in the ACA (no single payer being a glaring one), their whole strategy of 'repeal and replace with nothing' has now been shown to be a guaranteed loser. Now they're faced with possibly turning the House over to the Dems in 2014 _despite_ the gerrymandering as a result of their internal civil war over whether or not it was a guaranteed loser.

And sure, the implementation is currently filled with varying levels of crap, but that's what you get when you let government (regardless of party) hire the programmers, as I alluded to above; the old "you get what you pay for" is very, very true for software work, and in the health care fields the best and brightest are currently firmly ensconced in the private sector. *shrug* No surprise on my part.

Of course, with the scope of the problem narrowed to "The implementation was coded like crap", the only thing required to fix it is to get some _decent_ developers and give them some time. More bad news for the GOP.
 

ISF - Join now!

Every member here is approved by hand. No bots, no spam, just people who care about evidence and honest debate.

Membership is free!

Create your free account

Back
Top Bottom