LudditeCare: A Federal Agency That Still Uses Floppy Disks
In October, a post at Power Line noted how kludged together the Obama administration's attempt to socialize the health care insurance industry is -- which oddly makes sense: why shouldn't a 19th century leftwing scheme (socialized medicine) be reliant on 1990s-era outdated technology?
The front end technology is not the problem here. It would be nice if it was the problem, because web page scaling issues are known problems and relatively easy to solve.
The real problems are with the back end of the software. When you try to get a quote for health insurance, the system has to connect to computers at the IRS, the VA, Medicaid/CHIP, various state agencies, Treasury, and HHS. They also have to connect to all the health plan carriers to get pre-subsidy pricing. All of these queries receive data that is then fed into the online calculator to give you a price. If any of these queries fails, the whole transaction fails.
Most of these systems are old legacy systems with their own unique data formats. Some have been around since the 1960′s, and the people who wrote the code that runs on them are long gone. If one of these old crappy systems takes too long to respond, the transaction times out.
Amazingly, none of this was tested until a week or two before the rollout, and the tests failed. They released the web site to the public anyway – an act which would border on criminal negligence if it was done in the private sector and someone was harmed. Their load tests crashed the system with only 200 simultaneous transactions – a load that even the worst-written front-end software could easily handle.
When you even contemplate bringing an old legacy system into a large-scale web project, you should do load testing on that system as part of the feasibility process before you ever write a line of production code, because if those old servers can’t handle the load, your whole project is dead in the water if you are forced to rely on them. There are no easy fixes for the fact that a 30 year old mainframe can not handle thousands of simultaneous queries. And upgrading all the back-end systems is a bigger job than the web site itself. Some of those systems are still there because attempts to upgrade them failed in the past. Too much legacy software, too many other co-reliant systems, etc. So if they aren’t going to handle the job, you need a completely different design for your public portal.
A lot of focus has been on the front-end code, because that’s the code that we can inspect, and it’s the code that lots of amateur web programmers are familiar with, so everyone’s got an opinion. And sure, it’s horribly written in many places. But in systems like this the problems that keep you up at night are almost always in the back-end integration.
And while an earlier Democrat (who also had his own visions of socializing medicine; like I said, it's a century-old scheme) would have looked at it all and said that the buck stops here, naturally for Mr. Obama, this is an all excuse for why none of the problems of his namesake bill are his fault, as Charles C. W. Cooke wrote yesterday at National Review:
In his Chris Matthew interview yesterday, Obama pushed back against the idea that this was his fault. Per Politico:“The challenge, I think, that we have going forward is not so much my personal management style or particular issues around White House organization,” Obama said. “It actually has to do with what I referred to earlier, which is we have these big agencies, some of which are outdated, some of which are not designed properly.”
So, it’s the government’s fault, not Obama’s. It’s the design of the agencies, not Obama. Okay, fair enough. But then why isn’t he moving to reform those agencies? He’d certainly have Republican support for that, and, as we all know, he just wants to do “what works” and he’ll “work with anyone” who agrees with him.
This approach is eerily reminiscent of David Axelrod’s. “How could the head of the executive branch know about the IRS scandal?” Axelrod effectively asked:“Part of being president is there’s so much underneath you because the government is so vast. You go through these [controversies] all because of this stuff that is impossible to know if you’re the president or working in the White House, and yet you’re responsible for it and it’s a difficult situation.”
It is difficult, yes. The federal government has become vast and unwieldy. Which makes it all the more peculiar that the reaction of the administration to every problem is to grow the system that they simultaneously say is too big to manage.
But the problem is also the voters' fault as well: why does a nation that's obsessed with iPads and Android tablets, laptops and smart phones, and loves nothing more than to customize and program and fine-tune this technology so that it's individualized to the nth degree vote to give more and more power to a federal government that's organized around 19th century socialism, and reliant upon fax machines, floppy disks, and, until the late-1990s, vacuum tubes? I wonder if Obama supporter Terry Gilliam realized in 1985, when he was making Brazil, that he was shooting a documentary about America in 2013?
* Why yes, it does take a certain amount of chutzpah for a print-based newspaper, which at least once a year runs an article decrying the use of air conditioning, toilet paper, refrigerators, automobiles, and other inventions man has created to ease his brief time on this mortal coil, to complain about the Luddite nature of the federal government they worship.
Related: Damned if you do, damned if you don't: On the one hand, while Washington state's health-insurance website has been down for days, "federal health officials, after encouraging alternate sign-up methods amid the fumbled rollout of their online insurance website, began quietly urging counselors around the country this week to stop using paper applications to enroll people in health insurance because of concerns those applications would not be processed in time," AP reports today.
(Artwork created using multiple Shutterstock.com images.)