Robert Laszewski, a health care industry consultant, is skeptical that the health insurance exchanges' information technology failings can be mitigated in time to prevent chaos. "The fix might be to take it down and start over," he said. "I don't know what the best-case scenario for these guys fixing this thing is, but it's got to be two or three weeks, minimum."
Obamacare Website Failure Threatens Health Coverage For Millions Of Americans
I do not represent myself as a professional programmer, though I have received formal training in the discipline in my pursuit of an Information Technology degree over the past twenty years' worth of my varying interest.
Programmers work by creating a skeleton, then they "flesh it out" by adding discrete units of functionality. They will denote the locations on this skeleton where these units are to go, denoted with notes to themselves. These notes are called "remarks."
When you see a remark in the Obamacare code such as "Insert SSI eligibility code here," or some such, it means that the skeleton has not been fleshed out.
It's like when you build a house and walk around and write notes to yourself on the two-by-fours. "Window goes here." Or "Electrical outlet here."
The windows have not yet been installed in Obamacare.
And if the backend of the exchange software is as unready as the client side, which I have no reason to believe that it is not, Obamacare will take several years to get running. It will likely take five years.
It makes no difference anyway, as humans no longer trouble themselves with the snorts and the grunts issuing forth from that idiot jurisdiction.
The jurisdiction will be a distant memory by the time everyone's favorite big-government brainchild is up and running.
It's a United States law. Give it its due. Wipe your ass with it.
