• Security incident: ISF was recently accessed by intruders. Please change your password, and change it anywhere else you used it. Read more

Heeeeeeere's Obamacare!

It's kind of a big problem. Opponents of Obamacare are overjoyed, it's supporters who are angry.

If opponents of the ACA are overjoyed about this, they are freaking stupid. The problems with signing up for the ACA will get fixed. In the meantime, the massive amount of people trying to sign up is a good sign that the system is going to be extremely popular. Suck it, GOP.
 
If opponents of the ACA are overjoyed about this, they are freaking stupid. The problems with signing up for the ACA will get fixed. In the meantime, the massive amount of people trying to sign up is a good sign that the system is going to be extremely popular. Suck it, GOP.

Well I hope they get fixed soon. I'm reading that the problems may take months to fix. It's not just a few minor glitches, but some serious problems that can't just be tweaked on the fly. And the enrollment deadline is approaching.

IT experts: HealthCare.gov is still a mess
 
Just to be sure, people's biggest complaint now is they can't sign up for Obamacare fast enough?
:rolleyes:

FTFY. And yes. But unlike the cries of "communism" and "government takeover," this is a valid complaint.

People are on a timeframe. If they don't have coverage by mid-December, they're going to face fines. We're coming up on three weeks after launch, and there's no indication of when these problems are going to be fixed.

This is not political. This is an issue of basic competence in software development. It's rather clear at this point that the organizations that wrote this system knew more about securing government contracts than about developing software.
 
Well I hope they get fixed soon. I'm reading that the problems may take months to fix. It's not just a few minor glitches, but some serious problems that can't just be tweaked on the fly. And the enrollment deadline is approaching.

IT experts: HealthCare.gov is still a mess

Ugh. That confirms a lot of what I've been observing, and it doesn't give me the warm and fuzzies. Some serious pooch-screwing has been done here.
 
Well I hope they get fixed soon. I'm reading that the problems may take months to fix. It's not just a few minor glitches, but some serious problems that can't just be tweaked on the fly. And the enrollment deadline is approaching.

IT experts: HealthCare.gov is still a mess

Yup, that could be a big problem. Though it is one that could be addressed without too much trouble... simply push back the enrollment deadline. While this is not ideal, it's not like the sky is falling, either.

ETA: I also found this particular bit of the article interesting... it seems that you really do get what you pay for...

The problem might also have stemmed from the budget alloted to the whole project. Back in April, the Washington Post noted how building the health care exchange was estimated to cost at least $5 billion to implement. Congress alloted only $1 billion, so Health and Human Services patched together the needed budget from a number of other, different federal allowances. It's not hard to see how one of the victims of such a lean budget was a proper test framework for the needed infrastructure.
 
Last edited:
I'm no tech-head, but what I don't get is how some people (like Wildcat) are having a helluva time with the federal site, while other people (like me) are having basically zero problems. I just went to healthcare.gov a few minutes ago, logged in, and started shopping for insurance on the exchange with not a single glitch.

I don't get it :confused:
 
I'm no tech-head, but what I don't get is how some people (like Wildcat) are having a helluva time with the federal site, while other people (like me) are having basically zero problems. I just went to healthcare.gov a few minutes ago, logged in, and started shopping for insurance on the exchange with not a single glitch.

I don't get it :confused:

Same here Mattus, I've been having 0 problems. I go there daily just to see if there's an error that pops up. Then again, I live in North Dakota, and I don't think it's too flooded here. That being said, I highly doubt that they would enforce the deadline if they knew people couldn't sign up. That would just be stupid.

@Cleon, I wasn't sure if it was a web browser issue, I was just stating that it couldn't specifically be ruled out. Since sometimes Java doesn't agree with Safari. I agree though, it definitely shouldn't be something on the users computer or anything like that.
 
I'm no tech-head, but what I don't get is how some people (like Wildcat) are having a helluva time with the federal site, while other people (like me) are having basically zero problems. I just went to healthcare.gov a few minutes ago, logged in, and started shopping for insurance on the exchange with not a single glitch.

I don't get it :confused:

There's really no way to know for sure without digging around in the source code. However, some different logic paths might involve age, marital status, children, or even just the time of day.

Other possibilities are data corruption, which might have affected Wildcat but not you.
 
@Cleon, I wasn't sure if it was a web browser issue, I was just stating that it couldn't specifically be ruled out.

Sure, it could be an artifact of some bad data being sent by the client. However, if the app has that much client-side logic, it should be validated and sanitized before being sent to the server.

Since sometimes Java doesn't agree with Safari. I agree though, it definitely shouldn't be something on the users computer or anything like that.

Requiring client-side Java is itself horrible design, for precisely that sort of reason. Unless there's a damn good reason for it (eg, Netflix requiring Silverlight), the user shouldn't have to download anything in order to run a web-based application. That's kinda the point of having it web-based.
 
Last edited:
This is not political. This is an issue of basic competence in software development. It's rather clear at this point that the organizations that wrote this system knew more about securing government contracts than about developing software.

The problems with any organization that invariably turns to the lowest bidder rear their ugly head again...
 
This is not political. This is an issue of basic competence in software development. It's rather clear at this point that the organizations that wrote this system knew more about securing government contracts than about developing software.
I wonder how many ex-politicians and ex-government workers or otherwisae well-connected people they have on the payroll to ensure they get the contract? You now, the guys who know the right people and the right things to say to get the contract, which is usually far more important than competence and ability when it comes to such things. It's how Bill Daley, genius businessman, made his fortune.
 
The problems with any organization that invariably turns to the lowest bidder rear their ugly head again...

Yup, and while I'm not making any excuses for the folks at HHS, it looks as if this particular part of the problem falls on Congress. Referencing the most recent article cited in the thread, I would like to note that the Dept of HHS requested $5 billion for the rollout of the ACA, and then Congress funded it at only $1 billion.

No wonder they had to do this thing on the cheap. The lesson here: whether it's in private industry or through the government, you get what you pay for.
 
One of the articles above mentioned open source and GitHub. Is is funny because I was just thinking that they could have used that.

It turns out they did try, just incorrectly. First, they had it up. But it was one giant commit and was out of date. And it was only for the front end, so they got numerous bug reports for the back end in error. They also used a GLP v2 code and didn't give attribution. So then they just removed it all.

Saying these are amateur mistakes is too kind. It is more like your parent who wants to hang with the cool kids but just doesn't get it.
 
One of the articles above mentioned open source and GitHub. Is is funny because I was just thinking that they could have used that.

It turns out they did try, just incorrectly. First, they had it up. But it was one giant commit and was out of date. And it was only for the front end, so they got numerous bug reports for the back end in error. They also used a GLP v2 code and didn't give attribution. So then they just removed it all.

Saying these are amateur mistakes is too kind. It is more like your parent who wants to hang with the cool kids but just doesn't get it.

On this one aspect, I can sort of see why they might do this. In their Git repository, it's possible they had at some point committed more than code files, such as functional specs or internal documents. The way Git works is that when you get a repo, you get its entire history even if files have been deleted. In that circumstance, it'd be wise to copy the files over to a new folder, blow away the .git folder, and do a new initial commit from scratch. I'm not sure why they didn't include the back end, but maybe that had connection information to the actual back end or something. Either way, it didn't work out but I get why it didn't have any commit history.
 
Has anyone seen these "Creepy Uncle Sam" videos made by a group backed with Koch money?



I don't get it. No substantial argument is being made here whatsoever, besides "government is creepy". Could anyone possibly be fooled by this? Maybe it's only meant to appeal to people who already oppose Obamacare? Particularly the rich old people who are paying for it.
 
Obamacare is good for jobs.

Lucrative jobs at lobbying firms for the people who drafted it.

ObamaCare has become big business for an elite network of Washington lobbyists and consultants who helped shape the law from the inside.

More than 30 former administration officials, lawmakers and congressional staffers who worked on the healthcare law have set up shop on K Street since 2010.

Major lobbying firms such as Fierce, Isakowitz & Blalock, The Glover Park Group, Alston & Bird, BGR Group and Akin Gump can all boast an Affordable Care Act insider on their lobbying roster — putting them in a prime position to land coveted clients.

Read more: http://thehill.com/business-a-lobby...indfall-as-washington-lobbyists#ixzz2iF0TKPID
Follow us: @thehill on Twitter | TheHill on Facebook
 

ISF - Join now!

Every member here is approved by hand. No bots, no spam, just people who care about evidence and honest debate.

Membership is free!

Create your free account

Back
Top Bottom