Why Trust the Gov’t With Insurance When It Can’t Even Create a Freaking Website That Works?

It’s a simple question, really.

Healthcare.gov and its astounding 500 million lines of code has had a few, how shall we say, glitches. People can’t even log on. When they do, they find the wrong information about the healthcare they’re supposed to be buying. The whole site is dedicated to one thing, and the information about that one thing isn’t even factually correct.

But that’s not all. The site also times out. It gives confusing error messages. People have been duplicate enrolled (when they actually get enrolled that is, which apparently takes an amount of time somewhere between ‘hours and hours’ and ‘never’). Some data fields are completely missing. The system reports spouses as children. Some of the calculators on the site don’t even work. A calculator. Something that has been around in electronic form since the 1960s…

Yet, millions of dollars went into the new healthcare exchange site. MillionS with an “S”. As in plural. More than one. Actually, more than a hundred of them.

According to the Wall Street Journal, the whole shebang may have cost the American taxpayers $600 million dollars to implement:
If users found a few bugs in their iPads, [Kathleen Sebelius, secretary of Health and Human Services] argued, most wouldn’t consider them a complete disaster. Instead, they would recognize that technology is complicated, that errors are common, and they would wait for an update. Apple Inc., she added, has “a few more resources” than her department, so “hopefully [citizens will] give us the same slack they give Apple.”
That argument is as clueless as it is misleading. While it’s true that Apple is fantastically wealthy, its product-development costs aren’t necessarily greater than those of the federal government. As Fred Vogelstein reports in his coming book, Apple spent about $150 million developing the iPhone. The health-insurance exchange—which, let’s remember, is merely a website meant to connect citizens to insurance companies, something quite a bit less complex than Apple’s groundbreaking miniature computer—so far has cost at least $360 million, and possibly as much as $600 million.

So the government took more money than most people will ever see in their entire lifetimes and handed it over to a whole team of techies and, somehow, they can’t even make a simple website function at even the most basic level?

Now, let’s go ahead and add that to the fact that they didn’t even spend that money to write all of their own code, but instead, they reportedly “borrowed” some of the code (read: pirated) from a UK company:
The computer code that was stolen is called DataTables, and it is exclusively provided under a GPL v2 license which requires anyone who uses the software code to keep the copyright notice visible in the code itself. This allows the original author of the code to receive attribution for creating it.
An analysis of the code running Healthcare.gov reveals that the Obamacare development team maliciously removed the copyright notice and credit attributions from the code while copying and using the rest of the code. In the field of journalism, this would be called “plagiarism.” In the field of computer software, it’s called “piracy” according to the U.S. government. (source w/ screen capture of code comparisons)

Let’s be honest here. When is the last time the government even did something that was generally recognized as a smashing success anyway? Can you remember a time?

So the question, again, becomes:
WHY SHOULD WE TRUST THE GOVERNMENT TO MANAGE HEALTH INSURANCE WHEN IT CANNOT EVEN CREATE A BASIC FUNCTIONING WEBSITE?

I mean, at this point, most Americans wouldn’t pay the government $5 to make a noodle salad.

More importantly, after millions of dollars and several years of development, is it even possible to screw up something as potentially simple as a website this horribly bad and do it completely on accident?

Not believably.

So what is the ultimate goal of Obamacare, anyway? Continue reading

No comments:

Post a Comment