Category Archives: Technology and Society

How Congress Screwed Up Human Spaceflight

There’s a good piece over at the Washington Times:

Imagine what could be done if resources being thrown into the furnace for the Space Launch System was repurposed for technology incubation, commercial projects, or heaven forbid, actual missions. For the cost of SLS, you could afford close to 170 launches to the ISS, 55 missions to Mars with cargo or for probes, or more than 220 Falcon Heavy launches. There are opportunity costs to funding bad projects, and funding SLS costs mankind nearly 500 opportunities to actually go to space.

But it gets it wrong at the end:

When President Obama came to office, NASA was working on the Constellation Program, its most ambitious project in decades. The plan would have seen the United States return to the moon and establish a permanent base as a first step toward the manned exploration of the solar system. Fiercely lauded in the scientific and space community, it even earned the rare but ringing endorsement of Neil Armstrong. However, this highly ambitious project was clumsily canceled by the Obama administration in the name of cost-cutting in 2010 — only to be replaced with the government monstrosity known as SLS a year later.

No. A reader would imagine that Constellation was just peachy, but it was just as programmatically disastrous as SLS, slipping more than a year per year in schedule with continuously ballooning costs. It (like SLS) needed to be cancelled. The mistake of the administration was not in cancelling it, but in not working with Congress in doing so, or providing a coherent explanation of what the replacement was to be. Constellation may have been “fiercely lauded” by some in the scientific and space community, but it was just as fiercely, and justly, attacked as a barrier, rather than a mean of serious human spaceflight beyond earth orbit. It’s curious that Mr. Jacobs seems to understand the current problem without understanding the actual history that led up to it.

The ObamaCare Train Wreck

Thoughts from Richard Epstein.

Even its supporters are having trouble excusing it. Read this from Ezra Klein.

Hey, it’s not like this wasn’t perfectly predictable, and predicted.

[Update a while later]

Was the site crash caused by rate shock?

[Update a few minutes later]

Wow, even the New York Times is becoming racist:

“These are not glitches,” said an insurance executive who has participated in many conference calls on the federal exchange. Like many people interviewed for this article, the executive spoke on the condition of anonymity, saying he did not wish to alienate the federal officials with whom he works. “The extent of the problems is pretty enormous. At the end of our calls, people say, ‘It’s awful, just awful.’ ”

Interviews with two dozen contractors, current and former government officials, insurance executives and consumer advocates, as well as an examination of confidential administration documents, point to a series of missteps — financial, technical and managerial — that led to the troubles.

It’s almost like these people think politics is more important than actually competently running the government.

The Expensive ObamaCare Web Site

There is no good excuse for it:

From the evidence, it’s clear that the Obamacare exchange servers saw errors of all different kinds. They weren’t prepared for the load, even though this was never very heavy. California reported about 600,000 unique visitors, and Colorado reported about 55,000 unique visitors.

There were screen captures of database errors, not because the data was bad, but because the structure that holds the data was misdesigned.

There were 404 errors, which are totally design errors, meaning that the web sever was trying to get to a page that didn’t exist. (This led to the best hashtag of the day, #404care.)

There were non-descript server errors like the one I got from the California server.

There were user-interface errors. At about 10:00 AM, Colorado suspended new accounts on its site (it’s one of the ones using its own site, not the main exchange site), and didn’t get around to allowing new accounts again until 3:00 PM. At that point, the “New Account” button sent you to the login page for existing accounts. If you chose to enter your childhood phone number for a secret question, it wouldn’t take it, no matter what format (certainly not the format it used when asking for your current phone number).

This is why I say it was clear that this wasn’t just one of those things. The volume of inquiries wasn’t high by large-system standards, and the rest of the errors were in the control of the programmers.

These were design and execution errors, pure and simple. They were all catchable, with proper beta and load testing.

Yup.