News for hackers. Stuff that matters.
Re:Why getting the Obamacare exchanges to work was difficult by mkr-hn on Saturday October 05, 2013 @11:04AM (#6500855)
You sound like you know all the legal, technical, and regulatory issues they faced in designing the system.
Re:Why getting the Obamacare exchanges to work was difficult by jrockway on Saturday October 05, 2013 @11:20AM (#6500910)
I doubt there is a legal issue that would prevent the site from being statically served with ngnix.
Re:Why getting the Obamacare exchanges to work was difficult by mkr-hn on Saturday October 05, 2013 @03:12PM (#6501691)
> legal, technical, and regulatory

Three things.

Re:Why getting the Obamacare exchanges to work was difficult by jrockway on Saturday October 05, 2013 @11:28PM (#6502990)
Regulatory issues are legal issues. Why do people comply with regulations? To avoid the ire of the law.
Re:Why getting the Obamacare exchanges to work was difficult by mkr-hn on Sunday October 06, 2013 @06:39AM (#6503691)
I think I'm just frustrated with this whole ordeal of Silicon Valley Knows Best that we see when any kind of problem comes up. People get hung up on their pet theories and solutions and never stop to consider that they might be wrong.

It's impossible to solve a problem before knowing what the problem is. How can anyone here even begin to consider a solution before we know the problem? It's ridiculous. Maybe they're not allowed to use your favored solution. The solution is probably political, not technical. You can't fix an outdated/flawed policy with nginx.

It's just...weird. Half the posts in any politics thread at HN is people complaining about politicians coming up with pet theories and pet solutions for problems before understanding the problem, but they're so eager to do the same when the roles are reversed.

Re:Why getting the Obamacare exchanges to work was difficult by DennisP on Sunday October 06, 2013 @12:00PM (#6504429)
I wouldn't presume to suggest a solution to the larger problem of getting people signed up for plans.

But the problem right now is, people are very curious about what plans are available. It's public information that doesn't require personal data. The whole point of the exchanges is to give the public clear data on the available plans. Distributing public information is a problem that has been quite thoroughly solved.

The technical people didn't seem to realize that they had two problems to solve, not one. And my frustration right now is that part of Congress is trying very hard to defund the whole program before people are able to gain access to that information, and it should be too late for that.

If someone has screwed up the regulations so badly that this information intended for the public is not actually public, then of course that's where the problem is, but that seems unlikely to me. It would make for a very interesting news story, if true.

Re:Why getting the Obamacare exchanges to work was difficult by mkr-hn on Sunday October 06, 2013 @12:42PM (#6504556)
> If someone has screwed up the regulations so badly that this information intended for the public is not actually public, then of course that's where the problem is, but that seems unlikely to me. It would make for a very interesting news story, if true.

Healthcare.gov is covered in HN-popular libraries, software, and toolkits (like Bootstrap, jquery, and Drupal[1]), so the problem is apparently not that they just don't know any better.

It appears they went as far as they could with the latest and greatest tech. Someone somewhere along the chain of command failed to include a "provide any kind of useful information on the plans" provision in the design document. All signs point to this being either politics or negligence, not technology.

[1]I'm assuming on this one since WhiteHouse.gov has been covered in Drupal in the HTML and JS since the Obama administration took it over.

Re:Why getting the Obamacare exchanges to work was difficult by DennisP on Sunday October 06, 2013 @01:12PM (#6504643)
Drupal generates pages dynamically, usually from a database, which is the exact opposite of what I just suggested. Static pages are the way to go for very high volume. (And as dynamic frameworks go, PHP didn't actually do that well in the techempower benchmarks, though Drupal wasn't one they tested.)

Certainly the design is the root of the problem. You have to "apply" before you get any information. When I say that the team screwed up, I definitely include the people who designed it, not just the programmers who implemented it.

Re:Why getting the Obamacare exchanges to work was difficult by mkr-hn on Tuesday October 08, 2013 @10:00AM (#6514936)
I was right: https://news.ycombinator.com/item?id=6514775

Poorly-implemented technology was at the core, but it happened because of a flawed and entirely political process.

Re:Why getting the Obamacare exchanges to work was difficult by DennisP on Saturday October 05, 2013 @11:52AM (#6501026)
Prices and coverage of these plans is public information. For anything involving personal data they'd do the same thing they do now.

You'd want to adjust prices to account for subsidy but that's a simple function and you could do it clientside with javascript.