Live data from Hacker News

Healthcare.gov: Code by the People, for the People, Released Back to the People

theatlantic.com

31–40 of 42 posts

Re: Healthcare.gov: Code by the People, for the People, Released Back to the People

#31
This reads like the worst marketing mashup this year:

"We knew there were performance and reliability benefits from building the stack on HTML."

I know there are performance and reliability benefits from talking in English.

"You're just talking about content. There just needs to be one server. We're going to have two, with one for backup. That's a deduction of 30 servers"

I'm very happy the government decided to skimp on reliability for a public healthcare market.

"You can put Wordpress into Amazon but then you'll have problems; it wasn't designed to be a cloud application."

Wait wait wait Wordpress isn't a cloud app? Fuck, someone go tell Hostgator that--apparently it can't be done!

"Notably, the HHS team has been using feedback to drive design choices from the beginning, applying the 'lean startup' model to development."

Wow, even the lean startup namedrop.

I'd be a lot happier if, instead of putting the Obama webdev team on the gravy train, they spent that same money--you know--actually fixing healthcare. As it is they seem to be just doing free advertising and lead generation on the public dime for the insurance companies.

Re: Healthcare.gov: Code by the People, for the People, Released Back to the People

#33

This has not been "iteratively created on Github". It has one commit and 1 commit only. Just sayin... https://github.com/CMSgov/healthcare.gov/commits/master Still cool its open sourced though.

From what I know of the project, CMS has a GitHub enterprise account that they used internally to "iteratively create on github," this Repo is the one that moved over after release.

It's a big step to have government releasing ANYTHING on Github. And yes, it's the next logical step for them to start projects on GitHub. But they're not there yet -- its worth noting that neither Sunlight nor Code for America start their projects out in the open 100% of the time either. It's new ground, and government will, I think, move more towards developing out in the open as we progress. But for now, I'm pretty excited that they embraced technology from this decade.

I should note I'm the former Director of Sunlight Labs, and am an advisor to Code for America.

Re: Healthcare.gov: Code by the People, for the People, Released Back to the People

#34
post #23
post #20

I'm very eager to see how they handle the actual exchange code. Jekyll and static HTML make a lot of sense for a marketing/informational site (which this appears to be right now), but at some point, they're going to need a dynamic backend (right?). These exchanges will need to aggregate plan info from lots of different insurance carriers and display plans to people based on various bits of user-specific info. Perhaps…

One "website" can have multiple backends: static files prepared with Jekyl for the CMS part of it, and a full backend for any dynamic bits. You can feed both in the same page with judicious use of AJAX.

Of course. And if they do implement such a JavaScript-dependant approach, it will be entirely different from any other government site. As I said, I look forward to seeing how they progress.

Re: Healthcare.gov: Code by the People, for the People, Released Back to the People

#35
post #33

This has not been "iteratively created on Github". It has one commit and 1 commit only. Just sayin... https://github.com/CMSgov/healthcare.gov/commits/master Still cool its open sourced though.

From what I know of the project, CMS has a GitHub enterprise account that they used internally to "iteratively create on github," this Repo is the one that moved over after release. It's a big step to have government releasing ANYTHING on Github. And yes, it's the next logical step for them to start projects on GitHub. But they're not there yet -- its worth noting that neither Sunlight nor Code for America start thei…

As I understand it, that's correct: built using Github Enterprise internaly and then published publicly. There was code in public, on the Development Seed account, with respect to coding for the project; anyone can go look at the commits there. Your other points speak for themselves.

Re: Healthcare.gov: Code by the People, for the People, Released Back to the People

#36

This reads like the worst marketing mashup this year: " We knew there were performance and reliability benefits from building the stack on HTML." I know there are performance and reliability benefits from talking in English. " You're just talking about content. There just needs to be one server. We're going to have two, with one for backup. That's a deduction of 30 servers " I'm very happy the government decided to s…

I can think of any number of blog posts that pack more buzzwords per paragraph than this, but your experience may vary. http://mobile.slate.com/articles/business/moneybox/2013/05/d...

To your substantive point, no one skimped on reliability here. The content was pushed into Akamai precisely so it would always be available, quickly, to end users. Reducing servers in this context isn't skimping -- it's saving money by using modern Web tech. Developing this site also wasn't an option, as your comment implies: the law required its development and deployment. If you'd like public funds directed elsewhere, call your Congressional representatives.

Re: Healthcare.gov: Code by the People, for the People, Released Back to the People

#37
post #7

Last week, the United States Department of Health and Human Services (HHS) relaunched Healthcare.gov with a new appearance and modern technology that is unusual in federal-government websites. The article seems to be about a promotional/propaganda CMS for the government, am I missing something? "This is such a lean site," said Jon Booth "This is our ultimate dogfooding experience," said Eric Gundersen "The work that…

tbf, there is a good social engineering function to propaganda. Propaganda is not necessarily false, it just can be. If you look at the roots of the word (which originates with the Jesuits) it has the same meaning as "to go viral" in modern Internet speak. To propagate, to organically spread and grow on its own.

My father, who worked with MLK and the SCLC referred to his work in the civil rights and union movements as being "a propagandist for the right reasons" -- a dry jest that should have made your brain trainwreck instantly if you are paying attention. He was an incredibly smart and funny -- and very ethical man. I inherited the family business, which is why I ended up as founding executive director of the Tor Project. You of course are welcome to judge that bit of work on its own basis. I didn't write the software, I just took it from a framing as a gray hat cypherpunk project to being the acclaimed champion of human rights, journalism, democracy rights activists, and apple pie in about six months flat along with seven figures of funding most of it from the US government without which we'd probably be dead meat from the NSA now (IMNSHO, and I don't speak for the current project's management -- only a volunteer these days).

Ultimately, my point is, I've worked with folks in government, and around Alex. And I've worked around these health care exchanges from RomneyCare here in MA.

The fact that they can relaunch, have a database like this work, even get this decision through, is pretty damn revolutionary. That it worked and they didn't get immediately hosed for it -- you have no idea how risky this was for them on an eGov basis, especially in "obamacare" where they have targets on their back for everything.

Give the dudes credit for a little excessive celebration. It's not propaganda -- and if it were...?

Triangulation sucks too.

Re: Healthcare.gov: Code by the People, for the People, Released Back to the People

#38
post #25
post #8

The use of Jekyll (or any static HTML generator) is a really huge, positive conceptual step. I mean, we can now make edits -- in Markdown -- to individual blog posts and submit pull requests. Whether they actually honor those requests* is another thing, but this is a really cool step. Even the use of Markdown means that the site/content designers have to really work to obfuscate the content with unnecessary modules/w…

The huge leap that has to be made for Federal Government CIOs is the psychological attachment they have made between software that works and huge price tags. Sometime, long before I ever came along, CIOs in the Federal sector became convinced that the only way for software to work was for it to be big, sold by SAP/Microsoft/Oracle, and have a huge pricetag. Anything else is a huge risk in their world. They just don't…

"Nobody ever got fired for choosing IBM."

Re: Healthcare.gov: Code by the People, for the People, Released Back to the People

#39

This reads like the worst marketing mashup this year: " We knew there were performance and reliability benefits from building the stack on HTML." I know there are performance and reliability benefits from talking in English. " You're just talking about content. There just needs to be one server. We're going to have two, with one for backup. That's a deduction of 30 servers " I'm very happy the government decided to s…

I can think of any number of blog posts that pack more buzzwords per paragraph than this, but your experience may vary. http://mobile.slate.com/articles/business/moneybox/2013/05/d... To your substantive point, no one skimped on reliability here. The content was pushed into Akamai precisely so it would always be available, quickly, to end users. Reducing servers in this context isn't skimping -- it's saving money by…

but that doesn't seem super innovative. others in government have used akamai as origin servers--TSA then DHS did this in 06 and got rid of a bunch of servers.

Re: Healthcare.gov: Code by the People, for the People, Released Back to the People

#40
post #10

So, does this mean they learned some important lessons from the $18 million recover.gov site? As for Percussion, is the Sivak person saying that it takes a month to make a simple navigation change? Is this really about the CMS or the red tape involved in getting approval to make the change?

There's a lot to be learned from Recovery.gov, not all negative. In this case, the HHS CTO was referring to a change in the CMS itself, not the website(s) it controls. Getting code updated in the normal .gov contractor/sub-contractor model would generally take more time, both in terms of requirements and implementation.

I am skeptical. Seems more in the implementation of the CMS. Not a fan of percussion, but I have seen drupal implementations that tied content to presentation also take an stunningly long amount of time for a navigation change. Bad design. Bad implementation.
Post reply on HN