Skip to comments.'Best and brightest' techies drafted to fix Obamacare computer glitches
Posted on 10/20/2013 6:14:01 PM PDT by NormsRevenge
Two big problems hit the Obama White House on Oct. 1: the government shutdown, which saw hundreds of thousands of federal workers furloughed, national parks closed, and other disruptions. And the launch of the Affordable Care Act, which was always going to be tricky.
The first problem was solved temporarily, at least when Republicans and Democrats worked out a stop-gap spending deal, also heading off (for now) a government default on its debts. By most accounts, the White House came out the winner, although President Obama was careful not to beat his chest too much about it.
The second problem the presidents signature achievement so far, known as Obamacare has only gotten worse.
The White House reported this weekend that about 19 million people have visited HealthCare.gov and 476,000 individuals have applied online for health insurance.
But officials have yet to say how many people have actually bought a policy. In any case, it's a long way from the 7 million people the administration wants to see enrolled for health insurance through online exchanges during the six-month sign-up period.
Computer glitches seem massive. USA TODAY reports that "the federal health care exchange was built using 10-year-old technology that may require constant fixes and updates for the next six months and the eventual overhaul of the entire system."
Obama, presumably, has been asking sharp questions of his staff.
"I think that there's no one more frustrated than the president at the difficulty in the website," Treasury Secretary Jack Lew said on NBC's Meet the Press Sunday.
The coming week should see significant political activity surrounding Obamacare.
Obama is scheduled to speak about it at a health care event Monday.
(Excerpt) Read more at csmonitor.com ...
Epic Fail The Sequel
Does anyone still remember how to write code in Basic anymore?
We’re talking about a stupid computer program. There is no reason for failure. We have millions of these programs...all devised to catch people at “whatever”...so we’ll all be criminals together.
Spaghetti code, if that’s what it is to reflect the 2,000+ page law and 30,000 (!) pages of regulations, is not fixable.
I can see it now. Hundreds of Ivy League professors put on the payroll to supervise a 16 year old kid to fix it. If one supervisor is good, hundreds must be “more better”.
*sigh* You can’t throw 9 women in a room and make a baby in a month. (Old saying at my former employer) But they will try....until the finally realize that this monstrosity can’t be fixed this way. I wonder which of them will tell the Pres the emperor has no clothes.
I'm sure that was built into the system by design. More money for Obies campaign contributors.
The president is signing up? Har har....laugh a minute this jerk is.
“I’m gonna write me a minivan.”
And the WH got all this data from a screwed up website that doesn’t work. LOL
They spent $600 million and did’t have the best and the brightest?
Best and Brightest = OFA script kiddies with confidentiality agreements.
Wait until this monstrosity really gets going.
How convenient, huh. Oh we only need another couple billion... (lather, rinse, repeat)
Biggest glitch is the out of reach pricing in return for the high deductible and lower quality of care.
Let’s hope they do better than the morons involved with Fulfillment By Amazon.
“The Mythical Man-Month” by Fred Brooks, first published in 1975, discusses the phenomenon that adding workers to a late software project only makes it later.
the best and brightness understand how bad this is... and will embed bugs, back doors, and crashes all triggered by external means
should be interesting
meanwhile... where’d our $450m go??
Brooks's law is a principle in software development which says that "adding manpower to a late software project makes it later". It was coined by Fred Brooks in his 1975 book The Mythical Man-Month. The corollary of Brooks's Law is that there is an incremental person who, when added to a project, makes it take more, not less time. Brooks adds that "Nine women can't make a baby in one month".
And a lot of GOPe support ObamaCare, refused to fight for defunding and even postponement
In my experience it is much more difficult to fix someone elses code than it is to write it correctly in the first place.
As with everything else with this administration, they no doubt looked to give the contracts to political cronies.
These cronies likely bought their BMW's and travelled to the Caribbean on our dime; why should they feel compelled to do the work after getting free money?
if you’re approaching a critical deadline... and the system is pure failure... adding more people can work. I say this with decades of experience
the trick is to identify and remove the failing pieces as you add new ones thru a strict filter to insure capability
I’ve been brought into many projects and turned certain failure into stunning success in short order.
...The second problem the presidents signature achievement so far, known as Obamacare has only gotten worse...
The president’s signature achievement is working as planned. Destroy the private insurance industry and extort single-payer from the rubble.
It could get interesting, though. What actually is happening is that programmers are going to have to rewrite legislation, or pick which pieces will be acted on and which, ignored. That's not exactly how government is supposed to work around here...
Are they choosing repair people thru the same set of lenses that they used to draft the original language?
If so (and that’s probably the case), I expect more of the same incompetence with no remedy.
and remember how in 2009 how angry the right/GOP got whenever we were seeing Obama/Pelosi/Reid pushing everything thru before even reading/testing it? LIKE SOLYNDRA and THE CHEVY VOLT !!!!
This “glitch” is just another scheme to steal millions and give it to people who already have millions.
Actually if you put 9 women in a room and stagger their pregnancies, nine months down the road you could start having a baby a month. And that’s probably what will happen with obamacare. They’ll stagger it into the future.
the rule base shouldn’t be a big deal ... and can be done almost in parallel by teams of people
the core system interfacing to the users would also be trivial.
hell, during the same week they barely got 50,000 thru their system... a system I’ve got running at home was managing numerous requests, live, for 200k+ across the US and the EU. 200k+ unique people... multiple requests each.
all on a win7pro box that I got from a Panasonic division shutdown for $200.
I could easily get their bs running... or at least design / coordinate the teams to bing it together... but then I’d be no better then 0failure and crew.
sorry, but I won’t help bury my country for any price. unfortunately, there are many that will. principal and integrity are in short supply these days
Nice that your so confidant, but I doubt it. It has to interface with a dozen fed systems and some of the data it needs is in flat files....
Slave labor is always the most motivated. Or not.
The best and brightest techies are the hackers so we can expect lots of embedded problems.
I’m an attorney and a code jockey. The legislation is incomprehensible. The regulation is worse. How do you get usable requirements from a web of interconnected, cross-referenced, external law referenced, and intentionally vaguely written liberal fantasy law that nobody gets except their personal favorite parts? That’s where the rule base is going to come from? Not likely. No doubt that’s where at least some of the garbled data is coming from for the insurers. Other data issues are probably based on trying to match fields in assorted remote dbs that have a myriad of different normalizations, and fields that should match have the data in incompatible formats. But nothing is so irresolvable as unknowable requirements.
much of the IRS data
On top of that, wait until the entire system is supposed to "go live" instantly at every hospital, pharmacy, doctor's office, clinic, and government agency. And everybody logs on at once (like a Monday morning),and starts updating stuff. And expects the changes to be available instantly to the millions of people using the system. Massive crashes from traffic tsunamis that will happen from time-to-time. (Like "daily").
The system has to be built to handle peak stresses at least 100x greater than daily activity. Assuming it ever works with more than 4 or 5 real users logged on at any one time in the first place. Anything less than sub-second response time will lead to revolt. And I'm sure they have the safety and redundancy of the world's largest system outside of the NSA all figured out already.
This is the easy part, the slow manual entry of original data, with plenty of time (measured in months, rather than milliseconds) to get things right.
IRS? That’s hard to believe.
“IRS? Thats hard to believe.”
look at in the context of the 80’s. The biggest disk drive was a couple hundred meg. Data was archived on 9 track mag tape... Even the drives to read this data were all gone by 2000.
Now they can store and sort a lot, but if you go back a few years they couldn’t.
Sure. But Basic was abandoned totally when Windows took hold. Pity.
As an engineer, it didn't take me long to learn and apply it to solve every possible engineering problem, from Astronomy to structural engineering, hydraulics, coordinate geometry.
Even on Commodore 64s!
The best version I ever used, HP Basic, was never ported to truly fast microprocessors. I often wonder how far interpreted basic might have gone, or how popular it would still be, when run on a microprocessor with a speed of 3.4 GHz instead of 500 MHz.
Anyone, literally, with mastery of high school math could use Basic to do almost anything.
Don't know what you're talking about.
Fulfillment by Amazon has worked for me for years with no glitches that I can remember.
What would motivate the ‘best and brightest’ to ever want to kill this job?
Don’t get me started. One of the absolute worst experiences of my life.
I suppose I’m just a moron compared to someone of your exemplary capabilities. I’ll try to do better in my next life. In this life, I’ve taken my business elsewhere, and am dang happy for it.
file formats are a nonissue. encapsulate the format and move forward.
interfacing with multiple agencies are a non-issue... just define the gateway objects and move on.
it’s all data storage, data shuffle and business rules.