Uh oh: HHS still discovering new bugs in ObamaCare website as known ones are fixed

posted at 5:21 pm on November 7, 2013 by Allahpundit

A “tech surge” update via Ezra Klein’s Wonkblog. Spoiler: Sebelius’s “important announcement” tomorrow isn’t going to be “we fixed it.”

Today’s “Operational Update on the Health Insurance Marketplace” was not especially good news: As capacity problems at the start of HealthCare.gov get fixed, tech workers are finding new capacity problems later in the application process — ones that, up until now, they didn’t know about.

“Essentially what is happening is people are going through the entire process,” Medicare spokeswoman Julie Bataille, who runs the daily call, told reporters. “As we have fixed certain pieces of functionality, like the account creation process, we’re seeing volume go further down the application. We’re identifying new issues that we need to be in a position to troubleshoot.”

That means that, as the HealthCare.gov team ticks items off its “punch list,” it’s also adding new ones that need to be addressed.

Could be that I’m misunderstanding but that makes it sound like they focused on fixing the account creation process, a.k.a. the front end of the site, before they’ve fixed the back-end part that relays applicants’ information to insurers. Bob Laszewski, the health industry expert who’s emerged as a lead critic of the site, told Klein in an interview a few weeks ago that it’d be disastrous to repair the front end before the “834 transactions” on the back end were repaired. Many of those 834s are garbled or incomplete; the only thing that’s making them manageable right now is the fact that there are so few of them trickling in due to website problems that insurers have the time and manpower to clean them up. The front-end problems are basically a dam holding back a reservoir of tainted/screwed-up information. Fix them first and the dam will break before the reservoir’s been decontaminated/debugged.

Maybe they have fixed the 834 process and are now systematically cleaning up the application system so that enrollments can begin en masse. If so, though, I haven’t heard a word of it — and that would be something that O-Care fans, Klein and company foremost among them, would want to tout as shining proof that the tech surge is making strides. Laszewski published a status update about Healthcare.gov a few days ago on his own blog based on what his industry sources are telling him and claimed that progress in fixing the 834 problem is “incremental and nowhere near enough to be able to go to high volume processing,” leaving his sources pessimistic that HHS can possibly get this done by December 1. But then, that’s sort of the point of today’s Wonkblog piece — because they’re discovering more errors as they clean others up, there’s no reason to think they’re making any meaningful progress. As one to-do item gets checked off, another gets written in. Makes me wonder how much longer Obama will leave Senate Democrats out there to twist in the wind before breaking the news that December 1 just isn’t happening.

Via the Right Scoop, here’s Laszewski telling Megyn Kelly last night that he expects 80 percent of the individual insurance market to receive cancellation notices.



Related Posts:

Breaking on Hot Air

Blowback

Note from Hot Air management: This section is for comments from Hot Air's community of registered readers. Please don't assume that Hot Air management agrees with or otherwise endorses any particular comment just because we let it stand. A reminder: Anyone who fails to comply with our terms of use may lose their posting privilege.

Trackbacks/Pings

Trackback URL

Comments

Stick with:

Garbage in.

Obama Care Out.

APACHEWHOKNOWS on November 7, 2013 at 5:23 PM

Too, McAfee should get in the deal and save the U.S. by ID’ing this site as full on malware condusive.

APACHEWHOKNOWS on November 7, 2013 at 5:25 PM

The website can be cobbled together cosmetically but the back end where policy, transactions and system interfaces come together will NEVER work.

Mason on November 7, 2013 at 5:26 PM

This was the one aspect of Obamacare that I expected they would have gotten right, the website. The rest would just be an absolute nightmare of bloated and mismanaged bureaucracies pushing paper back and forth.

tommer74 on November 7, 2013 at 5:26 PM

NO WORRIES! If the site is not up, you can shop and sign up by phone. King Barack said so!

GarandFan on November 7, 2013 at 5:27 PM

Can’t wait to see what the next Explanation is come Nov. 30th.

Bitter Clinger on November 7, 2013 at 5:28 PM

This isn’t unusual in fixing software. When one process is finally working programmers discover that other processes aren’t.

As for the 834 problem, if that’s not fixed then not only will the insurance companies be in for a massive cleanup, but there will be many instances next year of people who think they bought insurance going to the doctor and discovering that they really didn’t.

seanhackbarth on November 7, 2013 at 5:30 PM

OT – but classic Carney.

MontanaMmmm on November 7, 2013 at 5:31 PM

First line of code: =Reach Fail First=

Last line of code: =Reach Fail or Else=

APACHEWHOKNOWS on November 7, 2013 at 5:33 PM

Well now that they are actually testing the system, of course they are going to find new bugs.

This is why large software projects schedule several months of testing.

The incompentence of the Obamacare Team is astounding!

wren on November 7, 2013 at 5:34 PM

Obama Lied, Your Health Coverage Died

Cicero43 on November 7, 2013 at 5:35 PM

As capacity problems at the start of HealthCare.gov get fixed, tech workers are finding new capacity problems later in the application process — ones that, up until now, they didn’t know about.

This was predictable from the start: every bug fix would uncover another bug. The system is garbage from top to bottom.

irishspy on November 7, 2013 at 5:35 PM

In this instance no true expert would be shocked. No new system is bug free. There are layers of bugs they haven’t even gotten to yet. Some bugs hide other bugs.

ConDem on November 7, 2013 at 5:36 PM

meh……they – the commie aholes – still won. So they look like shmucks for the moment. BFD- They can live with that, considering. At the end of the day they know the wheels are in motion. A collapse of the HC system was always their goal.
.
And America, is still screwed.
If anyone thinks this is not incompetent failure by design is clueless.
We will “need” Big Government more than ever to clean up the mess, once the HC industry goes tail-spinning into dysfunction.
They haven’t even read it to find whats in it. They don’t care.

FlaMurph on November 7, 2013 at 5:40 PM

what is really sick is that morons like obama and his cheerleaders have been put in charge of a system that gives everyone great healthcare. Highly exotic procedures and equipment and a workforce of very smart docs and nurses, etc, that actually work hard to help people

so on top of that we now have layers of government gumshoes doing what gumshoes do best, work incompetently and mostly in a desultory fashion

barry.bot gumshoes gumming up the system…

r keller on November 7, 2013 at 5:40 PM

Via the Right Scoop, here’s Laszewski telling Megyn Kelly last night that he expects 80 percent of the individual insurance market to receive cancellation notices.

What’s amazing to me is that the American people are going to do jack and squat about this. This OUGHT to be causing riots in the streets, but watching the example of Greece I don’t have a lot hope for citizen action.

Doomberg on November 7, 2013 at 5:40 PM

Often you’ll make “fixes” in one area and the result is another thing is messed up. Coding is a tough business, and you’ve got to have the proper management and talent. But it shouldn’t cost a King’s ransom. A Stanford Computer Science professor said that his class could have produced the website for maybe 400k, 1/1000th of what the US govt spent. But it looks like the govt has got its management lines crossed, and you’re just not going to be able to code effectively if that’s the case, even if you spent $400 billion on the site. The govt needs to clear the slate, not only of all the jumbled code, but of the associated management, and get a whole new team and start over from scratch.

anotherJoe on November 7, 2013 at 5:40 PM

Obamacare is a 72 Pinto with a blown engine, front end damage and currently ON FIRE. Liberals think it needs a tune up and will be ready to race in Le Mans. Maybe, just maybe, the overpriced radio and aftermarket rims are salvageable.
That reminds me – I am running low on pop corn.

LarryinLA on November 7, 2013 at 5:41 PM

Until Mama Cockroach Sebelius gets the bum’s rush out of HHS the biggest “bug” in the O’Commiecare racket (besides the Kenyan Dictator) will remain soiling the nest.

viking01 on November 7, 2013 at 5:41 PM

I think they’re just desperate to get a “See, you can go from Point A to Point Z in the enrollment process now” spin. Knowing dang well behind the scenes that the data is crappy as hell and the calls are sending corrupt data. At least if they fix the front end first it will at least seem like all is well to the idiot voters out there.

nextgen_repub on November 7, 2013 at 5:41 PM

Hopefully they are using the latest versions of WordPerfect and QuatroPro to make it run smoother…

DanMan on November 7, 2013 at 5:41 PM

This is hardly unsurprising given the state of Healthcare.gov at launch and the massive complexity built into the process by the 2200+ pages of legislation and 12k+ pages of regulations that define how things happen.

The exercise they are going through is similar to trying to patch cracks in the dam before the dam bursts, but every time you patch one crack, another one is created or found. Even in the private sector, on IT development projects, it’s not uncommon to introduce a new bug into a system for every four bugs ‘fixed’. Fix one dependency and another one upstream or downstream may suddenly stop working as intended.

The hardest thing to fix, however, are the fundamental architecture errors made in the software – things like the 834 problem which impacts the data being sent to the insurance companies (and ultimately the insured). With the scalability and data issues, I know there are serious design and architectural issues with Healthcare.gov.

I suspect that the WH is already working on the damage control for spinning HHS missing the end of November date for ‘fixing’ Healthcare.gov. Question is – what will the Democrats running in 2014 say about missing that date or the ‘damage control’?

Athos on November 7, 2013 at 5:42 PM

I think this needs to be said, John Roberts ruling in favor of Obamacare was almost like a Trojan Horse in its effect. His ruling allowed the natural decomposition occurring within the Administration to explode the whole rotten facade of the Obama Administration.

Dare I say it? Thank you Justice Roberts.

richardb on November 7, 2013 at 5:42 PM

For the tech guys here.

Is is possible they wrote the code in front of a mirror and did not notice the refraction problem?

APACHEWHOKNOWS on November 7, 2013 at 5:42 PM

Can’t wait to see what the next Explanation is come Nov. 30th.

Bitter Clinger

That’s easy. Take your pick: Richie Rich and the rich and their evil insurance companies! House GOP! The Tea Party! Ted Cruz! Rand Paul! Sarah Palin! Boooooosh!

ugottabekiddingme on November 7, 2013 at 5:43 PM

Just shop around…

d1carter on November 7, 2013 at 5:43 PM

Carney: Nov. 30 Deadline ‘Never Meant There Would Be Zero Problems’ with Healthcare.gov

http://www.youtube.com/watch?v=cEXtksnnrRg

whatcat on November 7, 2013 at 5:44 PM

McAfee should get in the deal and save the U.S. by ID’ing this site as full on malware conducive.

APACHEWHOKNOWS on November 7, 2013 at 5:25 PM

Post of the Day™

JusDreamin on November 7, 2013 at 5:44 PM

I think this needs to be said, John Roberts ruling in favor of Obamacare was almost like a Trojan Horse in its effect. His ruling allowed the natural decomposition occurring within the Administration to explode the whole rotten facade of the Obama Administration.

Dare I say it? Thank you Justice Roberts.

richardb on November 7, 2013 at 5:42 PM

No – it was luck on his part and is mortally wounding our economy. As fun as gloating is, the price is too high.

LarryinLA on November 7, 2013 at 5:45 PM

I mean seriously. I am a web developer and I guarantee I could have done this in 6 months for $60k.

The Notorious G.O.P on November 7, 2013 at 5:46 PM

Obamacare is a 72 Pinto with a blown engine, front end damage and currently ON FIRE.

Back in the day I had a buddy whose Pinto threw a rod that knocked a hole in the block. It still ran on three cylinders though! I had the ultra slick Vega GT with the pot metal block that blew smoke like an mosquito fogger at the time. I think his bucket actually ran better.

DanMan on November 7, 2013 at 5:46 PM

Dare I say it? Thank you Justice Roberts.

richardb on November 7, 2013 at 5:42 PM

Nope, no thanks. We’re looking at 100 million Americans being stripped of their health insurance and taxed for the privilege of it. There’s a good chance this could collapse the economy. Roberts totally failed in his basic duty to the constitution; and more than that, the American people are going to suffer irreparable harm all due to him.

Doomberg on November 7, 2013 at 5:48 PM

DanMan – We put 250k on a 72 pinto and sold it running. Two hard accidents in it too. Now it would no longer go over 55 on the freeway but it was still running ;)

LarryinLA on November 7, 2013 at 5:48 PM

Hopefully they are using the latest versions of WordPerfect and QuatroPro to make it run smoother…

DanMan on November 7, 2013 at 5:41 PM

Not to mention Paradox for their database….

Athos on November 7, 2013 at 5:48 PM

That’s easy. Take your pick: Richie Rich and the rich and their evil insurance companies! House GOP! The Tea Party! Ted Cruz! Rand Paul! Sarah Palin! Boooooosh!

ugottabekiddingme on November 7, 2013 at 5:43 PM

Yep!!

Palin, Cruz, and the Tea Party wrote the code.

Or least own CGI.

Something like that.

Bitter Clinger on November 7, 2013 at 5:50 PM

@AP: frontend is the HTML, CSS, JS, etc. the user interface. It’s what puts the data together for the user to interact with. The backend is the database, data processing and networking required to store the data and forward the processes to the insurance companies. The frontend being broken prevents bad data getting persisted and forwarded by the backend. There is no way they can fix this in the short term with any degree of confidence because what builds your confidence in software is extensive testing, But healthcare.gov is already in production. Even if you could test any one part of the code in QA or staging, you would have to make a mammoth effort to mock the DB and network processes that are in production and nowhere else. Meanwhile, the site is live and people are feeding data into the system which may be incomplete or completely absent without the user ever knowing.

daddytype on November 7, 2013 at 5:51 PM

NO one possibly could ever have foreseen this coming. No one. And, as we all know, it’s all the insurance company’s fault for being so gosh darn greedy. And Republican obstructionism! Revenues! Racism!

PetecminMd on November 7, 2013 at 5:51 PM

Perhaps Obama & Co could consider simplifying the Obamacare system by removing the Voter Registration functionality.

But, alas, Team Obama always believed the Voter Registration function was the most important part of the Obamacare system.

wren on November 7, 2013 at 5:52 PM

Damn those Germans, they don’t know how to write code and look what a mess they got Barky into!!! /s

NapaConservative on November 7, 2013 at 5:52 PM

When you fix bugs in a crappy system you will invariably get more bugs.

Wigglesworth on November 7, 2013 at 5:52 PM

“Go to warp drive” destruct phase.

APACHEWHOKNOWS on November 7, 2013 at 5:53 PM

i guess everything is okk now…deal leader has said he’s sorry about all those peasants that are in a tough spot

http://usnews.nbcnews.com/_news/2013/11/07/21352724-exclusive-obama-personally-apologizes-for-americans-losing-health-coverage?lite

r keller on November 7, 2013 at 5:54 PM

JustUs Benedict Roberts is a bastard coated bastard with bastard filling. May his name be forever associated with traitors.

The Lord Haw Haw robed pimp of Obamacare.

viking01 on November 7, 2013 at 5:54 PM

guess everything is okk now…deal leader has said he’s sorry about all those peasants that are in a tough spot
http://usnews.nbcnews.com/_news/2013/11/07/21352724-exclusive-obama-personally-apologizes-for-americans-losing-health-coverage?lite
r keller on November 7, 2013 at 5:54 PM

The only apology I will accept would have to be followed by the resignations of Obama, Biden, Sebelius and then Roberts.

LarryinLA on November 7, 2013 at 5:56 PM

Hopefully they are using the latest versions of WordPerfect and QuatroPro to make it run smoother…

DanMan on November 7, 2013 at 5:41 PM

Is it true that they’re programming with punch cards?

BuckeyeSam on November 7, 2013 at 6:00 PM

Well how can the eeeevvvviiilllll insurance companies deny people coverage due to bad data until the government hands them the bad data so that the insurance companies can be blamed?

It’s all Germany’s fault.

Or Canada’s.

Why did we stop blaming Canada? That is where the company is that made this junk…

ajacksonian on November 7, 2013 at 6:00 PM

Hey, I think they’re getting there :

Progress

MichaelGabriel on November 7, 2013 at 6:00 PM

I mean seriously. I am a web developer and I guarantee I could have done this in 6 months for $60k.

The Notorious G.O.P on November 7, 2013 at 5:46 PM

No offense, but NO … not when you have to tie to ALL those FUBAR’ed government legacy systems.

Clean slate … yeah … but legacy government systems are like trying to cure the measles by giving someone cancer.

PolAgnostic on November 7, 2013 at 6:01 PM

Why don’t we just cut through the crap?

The sole, singular purpose of healthcare.gov is to sell medical insurance.

A six-year-old can build a website to sell insurance.

franksalterego on November 7, 2013 at 6:02 PM

Best/truest article of the day.

Schadenfreude on November 7, 2013 at 6:02 PM

“Sir,, Sir,,, that is a cliff up ahead,,,,,”

“I am the all knowing Bill Ayers first production prototype, FULL SPEED AHEAD.”

APACHEWHOKNOWS on November 7, 2013 at 6:03 PM

A six-year-old can build a website to sell insurance.

franksalterego on November 7, 2013 at 6:02 PM

But then you deprive three two year olds of gainful employment!

ajacksonian on November 7, 2013 at 6:03 PM

Sorry, wrong link.

This is the one for today.

Schadenfreude on November 7, 2013 at 6:05 PM

It is not going to make any difference now no matter what they do even if they fix the stupid website… The Obamacare disaster is now hated more than ever and no amount of lies and blames by Maleek and his gang is going to change this… The good news is that the dumb liberals think that it is not a problem for them politically…

mnjg on November 7, 2013 at 6:05 PM

The audacity of dopes.

pambi on November 7, 2013 at 6:05 PM

Of course they’re fixing the front end first. Liberalism is all about appearances; functionality isn’t a concern. That’s why the word “Affordability” was mixed in to the name of the Act even though actual affordability was never even rationally considered. It’s why ever major piece of liberal legislation must be sold as something else; why “messaging” is so important to liberals and why every time their legislation is shot down by public opinion, it’s deemed as a failure of messaging.

All that matters for HHS is that person X can go from point A to B. That the insurance agency has to spend multiple hours parsing through the mess that makes it to them won’t be newsworthy, and therefor not detrimental to their goals.

BKeyser on November 7, 2013 at 6:05 PM

Scroll down just a tad.

Schadenfreude on November 7, 2013 at 6:07 PM

http://usnews.nbcnews.com/_news/2013/11/07/21352724-exclusive-obama-personally-apologizes-for-americans-losing-health-coverage?lite

r keller on November 7, 2013 at 5:54 PM

WOW.. everything is great now… Those who lost their insurance and will be forced to buy more expensive crappy ones are rejoicing…

mnjg on November 7, 2013 at 6:08 PM

Could they at least add Word Paint to it so you have something to do while the hourglass spins…

hillsoftx on November 7, 2013 at 6:09 PM

OT: Fox News is crucifying Obamacare in its first ten minutes. No good news.

BuckeyeSam on November 7, 2013 at 6:10 PM

This isn’t unusual in fixing software. When one process is finally working programmers discover that other processes aren’t.

Except that they had 3-1/2 years to do it. If they had tested the front end in 2011 and fixed it in early 2012, they would have had the rest of 2012 and 9 months of 2013 to fix the back end.

The front-end glitches are the least of their worries. When lots of people CAN sign on and find out how much their premiums and deductibles increase, there will be he!! to pay…

Steve Z on November 7, 2013 at 6:10 PM

I think this needs to be said, John Roberts ruling in favor of Obamacare was almost like a Trojan Horse in its effect. His ruling allowed the natural decomposition occurring within the Administration to explode the whole rotten facade of the Obama Administration.

Dare I say it? Thank you Justice Roberts.

richardb on November 7, 2013 at 5:42 PM

That’s retarded.

ThePrimordialOrderedPair on November 7, 2013 at 6:11 PM

It’s like treating brain cancer by giving the patient a facelift.

2lbsTest on November 7, 2013 at 6:13 PM

It’s like treating brain cancer by giving the patient a facelift.

2lbsTest on November 7, 2013 at 6:13 PM

Wrong end of the body, wrong set of cheeks.

ajacksonian on November 7, 2013 at 6:17 PM

Wouldn’t it be priceless if one day in the near future, Obama and Sebelius receive an anonymous package containing a spreadsheet with all the personal information of everyone that has signed up at healthcare.gov? Oh, and the major news organizations too.

lfwest on November 7, 2013 at 6:18 PM

Has the emperor considered buying out Kayak for the “front end” of healthcare.gov so people can sign up for medical tourism trips to Costa Rica and India?

AltTuning on November 7, 2013 at 6:28 PM

There is a key phrase that makes this website work: BLAME DA FILMMAKER.

MaiDee on November 7, 2013 at 6:32 PM

OT: the hits keep on coming.

http://watchdog.org/114950/obamacare-loophole-fraud/print/

BuckeyeSam on November 7, 2013 at 6:33 PM

In my Application Architecture line of work, I refer to this as the “Leaky Pipe Syndrome.”

Picture this scenario. In a town there is an old, iron water main pipe that was laid beneath main street back before World War I. Recently, a wet spot has appeared in front of a certain shop, and water is welling up out of the pavement. Water pressure is down on the entire block.

Obviously there is a leak in the water main beneath the street in front of that shop, so you dig up the street, patch the leaky section of the pipe with a beautiful piece of stainless steel, and all is well, right?

Unfortunately, almost immediately, a different wet spot appears in front of a different store. Water pressure is STILL down. Repeat the process, and now a wet spot appears in front of a THIRD store, that was never visible before.

What is going on?

As each section of the pipe fails, it allows an outlet for the pressure on the overall pipe. Even though one spot has critically failed, as soon as it does the pressure is released on the rest of the pipe – the length of which is probably just about as deteriorated as the single point of failure.

When you fix that one spot, all that it does is smooth the flow there, and thus the pressure increases on the pipe until the second-most weak portion pops. Replace that, and the third-weakest portion blows. And so on, and so on…

Until you replace the entire pipe.

The exact same problem appears in processing the flow of data. If the entire process is weak, as you fix flow in the problem spot, it simple reappears in the next-weakest problem spot. You must eliminate them ALL in order for it to flow properly – and thus the requirement for end-to-end capacity tests (which HHS has admitted were not even started, let alone completed.)

The point of failure will be at the weakest point in the pipe. There will be no point of failure only when there are NO weak sections of the pipe.

It’s simple logic.

(That must be why the Democrats don’t get it.)

JohnD13 on November 7, 2013 at 6:36 PM

OT. Fox news reported that Manchin from WVA and some RINO are co-sponsoring a bill to delay the individual mandate for ONE YEAR.

Conveniently past the 2014 election. DON’T LET THEM DO THIS!

BacaDog on November 7, 2013 at 6:39 PM

“Bugs Are US.”

APACHEWHOKNOWS on November 7, 2013 at 6:52 PM

Clean slate … yeah … but legacy government systems are like trying to cure the measles by giving someone cancer.

PolAgnostic on November 7, 2013 at 6:01 PM

A classic Monty Python skit talked about curing foot fungus by placing small amounts of dynamite between the toes. When asked about results of this revolutionary treatment, the answer is exactly what I would expect from this administration:

“Three dead, nine wounded, and seventeen missing – presumed cured.”

JohnD13 on November 7, 2013 at 7:01 PM

In other news, Patch Tuesday is on Tuesday.

SomeCallMeJohn on November 7, 2013 at 7:13 PM

I’m starting to suspect that the company that hired the programmers to do this work used the ‘if you find a bug you get a reward’ style of management.

This was actually tried!

Worked great!

Programmers intentionally wrote bugs in the code so they could find them later and get rewarded.

Perfect incentive all the way around.

ajacksonian on November 7, 2013 at 7:15 PM

May this ruin the week end for a few.

Why has the Healthcare.gov site not been hacked?

1.No challenge?
2.Nothing to hack?
3.Not yet?

The answer most likely is all of the above. Sort of!
Wait until it gets on line with the health records by 2015. Then it will be a Gold mine.
Now for the sleepless nights. The site may not have any “really important stuff” in it yet and they may some day close it up and make it secure.

Of course “Ann A. Butt” would say the site may already be setup with malware, trap doors, back doors and robots to last a decade, just waiting for the future use. Now go back to sleep and bask in the endless lies of your Government.

jpcpt03 on November 7, 2013 at 7:28 PM

No offense to anyone who claims they could have put together this site with Dreamweaver and a couple of pots of coffee but although the front end was the first thing that didn’t work ( comically enough because there is no reason it couldn’t have been load tested without all the back end stuff) especially since everyone was apparently coding to an api — but the legacy garbage systems, CMS, IRS, etc etc were the ones that don’t scale this way because they were never intended to. The government hasn’t modernized them because quite frankly there is no stomach for the multi-year effort to turn one of these scrap heaps into a working modern system. Government contractors can’t ( won’t) do it because they make a fortune supplying the chewing gum and dental floss to keep this garbage running. They will continue to make a fortune after this current debacle has come and gone. Obamacare was just an extremely productive day at the trough.

nokarmahere on November 7, 2013 at 7:55 PM

Both John Roberts and Obama have that smug look on their nasty faces. I guess that is normal when one has $hit for brains.

mobydutch on November 7, 2013 at 8:26 PM

The way these things usually work, when under the gun to patch up a bad poorly tested design each quick “bug fix” made in a big hurry creates two or more bugs.

When you haven’t tested the system very much to begin with how do you know what those “bug fixes” are really doing without doing what is called regresssion testing?

Regression testing is standard practice in the software design and development industry. But how can you regression test when you never really thoroughly tested the damn thing to begin with? Most likely these quick fixes are going into production with minimal testing.

farsighted on November 7, 2013 at 8:48 PM

If you lie better, you get to be the Pres., then if you lie worse you get to be a Republican RINO.

APACHEWHOKNOWS on November 7, 2013 at 9:43 PM

On bugs: Then there is the odd way http://www.hotair.com/ reacts to post from registered posters.

APACHEWHOKNOWS on November 7, 2013 at 9:45 PM

Well now that they are actually testing the system, of course they are going to find new bugs.

This is why large software projects schedule several months of testing.

The incompentence of the Obamacare Team is astounding!

wren on November 7, 2013 at 5:34 PM

Yes, as I keep saying, if I’d been on this project and told “you only have two weeks to test”, I would’ve walked.

For those saying you can do it for $50K or $100K, or even $500K, you’ve lost your minds.

I have designed and built sites this big. My WAG for it initially was $100MM. I have built two successful $30MM sites, and this is bigger than the two of them combined.

Chris of Rights on November 7, 2013 at 10:34 PM

When the deadline is this impossible, the only things they’re going to worry about fixing are the visible ones. You can count on the backend being broken for a very long time.

There Goes the Neighborhood on November 8, 2013 at 2:41 AM

“…We’re identifying new issues that we need to be in a position to troubleshoot.”

Can you say “whack-a-mole”?

olesparkie on November 8, 2013 at 7:43 AM

This isn’t unusual in fixing software. …

seanhackbarth on November 7, 2013 at 5:30 PM

Yea. But we usually address these fundamental architecture design flaws during the design process and no later than the first refactoring sweep.

This occurs during the first half of the development phase – not after the rollout.

If we did this in the private sector, we wouldn’t be doing this for very long.

Tsar of Earth on November 8, 2013 at 8:03 AM

These clowns are using the public to test the system. They clearly had no plan or skills to test. They have no idea where the design flaws and bugs are. This system is mostly useless. The system and the law should be scrapped.

scboy on November 8, 2013 at 5:19 PM

I am a computer programmer. So here is some expert advice.

Programs work or they don’t. It all depends on the skill of the people writing the code and the direction given by those managing the project.

Programs that work may have small flaws, but they get the job done and the flaws can be worked through.

Programs that don’t work are so badly constructed, no amount of fixes will help. The more they are tinkered with, the more problems that will surface. You end up with a worst mess than when you started.

The Obamacare websites don’t work. No level of “Tech Surge” will help. This is a case where the only solution is to scrap everything and start over. Managers of such failed projects never have the humility to admit their blunder and do this.

But even with the a signup process that would work, that does not change the fact that people are having to pay more for less.

Take the websites as a metaphor for the stupidity of the whole program.

bartbeast on November 9, 2013 at 10:00 AM