21–30 of 42 posts
Sorry, not feeling very patriotic about this. "by the people, for the people, released back to the people." Meanwhile those of the people who are physicians have had their fees sequestered by 2% http://www.medscape.com/viewarticle/781630 and are awash in extra paperwork for trying to prescribe something as simple as diabetic test strips as funding is tightened: http://www.pharmacist.com/cms-cuts-reimbursement-diabete…
Sorry, not feeling very patriotic about this. "by the people, for the people, released back to the people." Meanwhile those of the people who are physicians have had their fees sequestered by 2% http://www.medscape.com/viewarticle/781630 and are awash in extra paperwork for trying to prescribe something as simple as diabetic test strips as funding is tightened: http://www.pharmacist.com/cms-cuts-reimbursement-diabete…
Your first link is login-only.
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…
Earlier quoted context omitted.
This would have been more evident if any of those people had been quoted in the story. It also would have made the story more compelling -- as it stands, it reads like a bunch of colleagues congratulating each other on what fine work they have done.
Fair point. And ouch, I think. Just so it's clear, I'm not their colleague -- and the contractors in question weren't obligated to praise CMS. I'd hoped that readers would find the perspective of the writer useful, in addition to the comments of the principals, whose interests are obvious. Thank you for the feedback.
If you are a government contractor and some reporter asks you about a government project, the response is going to be positive (or at least obfuscated) unless you would like to have no more government contracts.
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…
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 believe that something that takes so little money, man-hours, and time to implement can possibly satisfy their requirements and replace such a huge portfolio of bloated legacy systems.
I built a metadata management system in a few weeks as a "rapid prototype" for a branch of the US military. It satisfied all of their requirements, was fast, secure, and stable. It was storing all of the production data and was made to be production ready by simply flipping a switch. Then the CIO saw it.
"Wow, this is amazing. Can you give the code to Team X so they can build it in Sharepoint?" 8 months later, a stunted, awful version of my prototype was demoed. The thick-client interface was gone, replaced by the awful, non-responsive Sharepoint bullshit. The Postgres back end that cost nothing was replaced with an expensively licensed SQL Server DB. The Google-like "search as you type" capability that was in my "prototype" was gone. Infinite scrolling in the grids was gone. Did I mention that they force their users to use Internet Explorer 8 because of "security reasons"? Never in my life have I witnessed such a huge level of IT incompetences as that on display in the United States military. This is almost surely due to endless bloated budgets which allow wankers like this to continue to keep their jobs.
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…
Earlier quoted context omitted.
Is educating the uninsured about the provisions of a law that applied to them "propaganda?"
Sure, propaganda can be educational. I read white papers, ads or other industrial propaganda just like anyone. My first word was promotion and I added propaganda afterward, maybe it added too much negativity, sorry. On the other hand, when reading the article I was disappointed that the article wasn't about the actual exchanges to facilitate finding and purchasing insurance. It was about building a CMS to help the go…
The folks at Development Seed are doing really awesome work between Prose and MapBox and it's great to see them get some recognition for it. Also a great plug for Jekyll in general. While there can certainly be more worrisome factors than cost for a site, site performance should be one of the most important issues when launching. By completely getting rid of a backing database, page lookup times can be reduced dramat…
The folks at Development Seed are doing really awesome work I am also a member of the Development Seed fan club, having met many of the team members. Though, I feel like they should update their PR statement. Every time they are mentioned in an article, the Drupal past comes out: The startup first made its mark in the DC tech scene consulting on Drupal I think we can all agree that mentioning one's history working wi…
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…
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?