Skip to main content

Sympathy for the Devil: The Obamacare online disaster

So the web site the government built to allow people to sign up for the new healthcare exchanges doesn't work. I've read a lot about it and as far as I can tell, nobody has managed actually to sign up for an insurance plan. The one guy who claimed he had, turned out to be a fraud. The situation is so bad that Obama supporter Jon Stewart is making fun of it. (I'm not sure if the New York Times has even mentioned the problem, but then the Times isn't a real news source like the Daily Show.)

It's possible that the programmers of the site were (as has been charged) simply incompetent. That's what a number of the experts being interviewed by big networks are saying. But my guess is that this was a very complicated problem, and I wonder if anybody is competent enough to have built this boat so it floats.

I certainly don't want to cut anybody in the administration any slack at all. In the real world, Ms Sibelius would be looking for a new job right about now. And of course, the system should have been tested. The fact that it wasn't going to work on day 1 should have been known before day 1.

Nevertheless, I would like to offer a small, tentative and hypothetical defense of the programmers. (It's hypothetical and tentative because I'm making a lot of assumptions about the nature of the challenges they faced.) My guess is that the complexity of the so-called "Affordable Care Act" system (with its exchanges and plans and tax consequences and all the rest) probably makes Amazon's database look like a recipe app. And to make matters worse, there have been various changes to the details of the law since it was first passed. The more complex the system, the more difficult it will be to incorporate changes in the rules the system observes.

So I do feel a wee bit of sympathy for the programmers.

Comments

Popular posts from this blog

Setting up OAUTH with Google in FileMaker 16

Setting up OAuth with Google in FileMaker 16Posted by William Porter Intended audience: Intermediate to Advanced FileMaker developers Date of publication: 2017-June-06
One of the many exciting features in FileMaker 16 (released last month) is OAuth or Open Authentication. Open Authentication allows users to connect to a FileMaker database after authenticating with an external (non-FileMaker) account. At the present time, FileMaker supports OAuth through Google, Amazon and Microsoft.
If you're a developer there are two main questions to answer. First, should I do this? And second, how do I do it? I'll answer the first question later. It's important.
But the other question--How do I setup OAuth?--is answered in the attached document. I wrote this tutorial with the help of my friend and colleague Taylor Sharpe of Taylor Made Services, also here in Dallas. We provide step-by-step instructions on how to get your users authenticating into your FileMaker databases using Google. (A…

Virtual List Basics

The conceptThe basic trick behind virtual lists is the wonderful GetValue() function. GetValue() takes two parameters: A list of return-delimited values A number specifying which value in the list to get

For example say you have a field in a single record called “List of Values” and it contains the following:

   Apple
   Boy
   Cat
   Doorknob
   Elephant
   Fish
When that record is selected, GetValue ( MYTABLE::List of Values ; 4 ) will return “Doorknob”.

The brilliant idea is to replace the list of values stored in a field with a list in a global variable.

The basic implementation, part oneCreate a table called VIRTUALLIST. In it, define these two fields: VALUE NUMBER: a number field Value_calc: calc field returning text value, = “GetValue ( $$VALUES; VALUENUMBER )”. Make sure that this value is an unstored calculation.

Go to the layout for the VIRTUALLIST table and create some records. Later you can create hundreds or thousands, but right now just ten will do. Use ReplaceFieldContents to po…

Getting out of fullscreen mode in FileMaker Pro

In version 2 of Acquittal, our criminal defense case management app, we're doing some nifty stuff with windows, and that means we're finding out that even in FileMaker Pro 15, we still don't have quite all the tools we'd like for managing windows.  One problem is how to trap for the possibility that the user has switched into fullscreen mode. The other problem is how to get out of it.


Is this window in fullscreen mode?
This one's not too hard. This calc formula seems to do the trick:

Get ( WindowHeight ) = Get ( ScreenHeight ) and
Get ( WindowWidth ) = Get ( ScreenWidth)

That will return true if the window is in fullscreen mode, false if it's not.

Why does this matter? Because there are certain things that you can't do with a window if it's in fullscreen mode. In Acquittal, for example, there are times when we want to generate a second "sidecar" window, then display the main and sidecar windows side-by-side. Can't do it if the main window …