In related news, We have ALWAYS been at war with EastAsia; We're from the Government, and here to help; I'll respect you in the morning, and; I'm a Lawyer, you can trust me. . .
Actually, he's taking charge of his own risk management, examining patches and determining if they're applicable. I seem to recall a McAfee update a few years back, that incidentally "bricked" a sizeable number of XP boxen. . .
Your main proposal is unworkable, simply because of the Tyranny of the Majority: it means all the Pro-City candidates would win for a state.
We already see area of states wishing to secede, because their legislatures are dominated by city folk. Because what's perfectly reasonable for a densely-populated city is often unworkable for rural areas. . .
Let me flip it back at you: How about a mod of the First Amendment for Political Campaigns:
1. Limited Time for campaigning: say, 30 calendar days prior to election
2. NO political Advertising, period. Each Candidate makes a statement on his or her stands on the issues of the day. Maximum length, 2 pages. All responses are in a booklet mailed to voters 10 days prior to the election.
3. No political parties.
4. One public forum for candidates: each has 15 minutes to sell him/herself and their ideas. Saved to web, and viewable.
I seem to recall the candidacy of one Hillary Clinton.
And as for the rest of the world's political spectrum, the US poltical spectrum is simply different. It probably has something to do with the Metric system (grin)
Two: massive requirements base to develop specification for development and implementation: The PPACA was 1800+ pages, and the associated regulations are 10,000+ pages, and are STILL changing. Can't develop without a spec and design, with big parts of requirements still changing.
Three: inadequate testing. The above-referenced link states that security testing BEGAN in August 2013, less than two months before rollout. There's no mention of load testing
Four: Integration issues. The Obamacare Exchange system combines data from numerous agencies and systems, and integrating between them is always a difficult task
Five: Identity-management. This is in parallel to Integration, somehow all identities need to be federated into a single overarching system.
Twenty-three months, even with a top-flight team, would simply not be enough to do this: this is a 5-7 year job. . .
Speak for yourself. Assembly is fairly clean, and the chips are going to be made anyway. And then, there's the savings in marine diesel from not having to ship it back from overseas. Lastly, I think we'd rather have the jobs over here. . .
. ..eats huge amounts of power, not large amounts of water for cooling.
And thus, power requirements go up, pushing the limits of your provisioned electrical infrastructure.
And extremely-high-capacity circuit breakers tend to be explody when they fail. My guess: someone used some REALLY bad assumptions for electrical infrastructure planning. . .
Software runs on hardware. Which you have to provision and configure. Security hardening and high-availability. Identity management, which is a BIG part in this. Integration between data sources. Comm lines and network infrastructure. Storage. Backup. Dev and Test environments. Software is only PART of the problem.
Look around, you'll find stories of various agencies trying to contract for T-class lines. . . in mid-September, to be in-place and turned-up by 1 October.
Consider Healthcare.gov as an Engineering project. Under.gov procurement rules. . .
The law: an ~1800-page CONOPS document.
The 10K+ pages of accompanying regulations ? User requirements.
So. ..CONOPS passes approval, User reqs start getting gathered. Someone writes an RFP and puts it out for bid. Given typical Fed procurement requirements, that's 9 months to a year before contract award. PPACA passed in March 2010, so we're probably at March 2011 now.
Winner ramps up, develops a Performance Spec and Initial Design, and starts procurement of infrastructure required. Another 6 months. Sept, 2011 now.
Infrastructure stand-up and development begins. Likely another 3 months. It's 2012 now. Standard development and monitoring/audits. Pilot of basic site for Insurance Exchange, though reviews and changes. 6 months min, 9 months likely, Sept 2012.
In the next year, you need to finalize, get the integration between multiple.gov sites and agencies hashed out and tuned, and THEN go to useability, security, and scaling tests. In ANY.gov program, that's 2 years, minimum.
Which means, the first REALISTIC date for Exchange eligibility would have been October 2014. But the lawyers and politicians didn't bother asking the ENGINEERS how long it would take, they never do.
And **THAT**, is my best estimate of what went on and what is going wrong. . .
Slashdot Mirror
Rumor has it, Miley and Justin are breeding the first generation of NEGATIVE-information voters. . . .
In related news, We have ALWAYS been at war with EastAsia; We're from the Government, and here to help; I'll respect you in the morning, and; I'm a Lawyer, you can trust me. . .
Actually, he's taking charge of his own risk management, examining patches and determining if they're applicable. I seem to recall a McAfee update a few years back, that incidentally "bricked" a sizeable number of XP boxen. . .
I'd like a few things FOR Congress. Tar and Feathers come to mind, for starters. . . .
Hence, I suggested it as a mod of the First Amendment. . .
Your main proposal is unworkable, simply because of the Tyranny of the Majority: it means all the Pro-City candidates would win for a state.
We already see area of states wishing to secede, because their legislatures are dominated by city folk. Because what's perfectly reasonable for a densely-populated city is often unworkable for rural areas. . .
OK, what do you suggest ??? Political Combat in Thunderdome ??
Two pols enter, one pol leaves. . .
It would certainly fix the geriatrication of Capitol Hill. . .
Let me flip it back at you: How about a mod of the First Amendment for Political Campaigns:
1. Limited Time for campaigning: say, 30 calendar days prior to election
2. NO political Advertising, period. Each Candidate makes a statement on his or her stands on the issues of the day. Maximum length, 2 pages. All responses are in a booklet mailed to voters 10 days prior to the election.
3. No political parties.
4. One public forum for candidates: each has 15 minutes to sell him/herself and their ideas. Saved to web, and viewable.
Yes. Many of us oppose Obama because of his color. We don't like Yellow-striped Reds (evil grin)
I seem to recall the candidacy of one Hillary Clinton.
And as for the rest of the world's political spectrum, the US poltical spectrum is simply different. It probably has something to do with the Metric system (grin)
"Don't Blame me, I voted for Kodos!!!"
- Homer Simpson
And the FIRST step to thoughtful debate is to STOP DEMONIZING YOUR OPPOSITION.
Obama is NOT the anti-Christ (that would be Larry Ellison. . .) and the Tea Party is not the KKK in Izod and Chinos. . .
Well, yes, if Cthuhlu was the alternative.
But for the most part, Brand D and Brand R are like toothpaste. Different flavors of pasty abrasiveness. . .
. . . and people who are experienced in developing and delivering in that maze of requirements.
If you have not been involved with engineering systems for the Feds, you would not BELIEVE the difference. . .
You forgot one element:
Cost-plus contracts. Otherwise known as "Pay-to-fail, then fix. . . "
One: Schedule Fail. Compounded by late award of the contracts to develop/influence:
Contracts Awarded Dec 2011
Two: massive requirements base to develop specification for development and implementation: The PPACA was 1800+ pages, and the associated regulations are 10,000+ pages, and are STILL changing. Can't develop without a spec and design, with big parts of requirements still changing.
Three: inadequate testing. The above-referenced link states that security testing BEGAN in August 2013, less than two months before rollout. There's no mention of load testing
Four: Integration issues. The Obamacare Exchange system combines data from numerous agencies and systems, and integrating between them is always a difficult task
Five: Identity-management. This is in parallel to Integration, somehow all identities need to be federated into a single overarching system.
Twenty-three months, even with a top-flight team, would simply not be enough to do this: this is a 5-7 year job. . .
Speak for yourself. Assembly is fairly clean, and the chips are going to be made anyway. And then, there's the savings in marine diesel from not having to ship it back from overseas. Lastly, I think we'd rather have the jobs over here. . .
The REAL question is. . . . which relative of which school board member(s) got a hefty "consulting" fee for persuading the District to do this. . .
Turns out I was optimistic. Apparently the contracts did not even go out for bid until late 2011, and testing began in August, 2013. . .
Gottlieb and Astrue: ObamaCare's Technology Mess
So, time for implementation was SEVERELY compressed, much less testing. .
Multiple on the fly changes are, alas, typical in Federal projects.
The Classic case of project fail due to this:
Who Killed the Virtual Case File ??
. . .eats huge amounts of power, not large amounts of water for cooling.
And thus, power requirements go up, pushing the limits of your provisioned electrical infrastructure.
And extremely-high-capacity circuit breakers tend to be explody when they fail. My guess: someone used some REALLY bad assumptions for electrical infrastructure planning. . .
Software runs on hardware. Which you have to provision and configure. Security hardening and high-availability. Identity management, which is a BIG part in this. Integration between data sources. Comm lines and network infrastructure. Storage. Backup. Dev and Test environments. Software is only PART of the problem.
Look around, you'll find stories of various agencies trying to contract for T-class lines. . . in mid-September, to be in-place and turned-up by 1 October.
Consider Healthcare.gov as an Engineering project. Under .gov procurement rules. . .
The law: an ~1800-page CONOPS document.
The 10K+ pages of accompanying regulations ? User requirements.
So. . .CONOPS passes approval, User reqs start getting gathered. Someone writes an RFP and puts it out for bid. Given typical Fed procurement requirements, that's 9 months to a year before contract award. PPACA passed in March 2010, so we're probably at March 2011 now.
Winner ramps up, develops a Performance Spec and Initial Design, and starts procurement of infrastructure required. Another 6 months. Sept, 2011 now.
Infrastructure stand-up and development begins. Likely another 3 months. It's 2012 now. Standard development and monitoring/audits. Pilot of basic site for Insurance Exchange, though reviews and changes. 6 months min, 9 months likely, Sept 2012.
In the next year, you need to finalize, get the integration between multiple .gov sites and agencies hashed out and tuned, and THEN go to useability, security, and scaling tests. In ANY .gov program, that's 2 years, minimum.
Which means, the first REALISTIC date for Exchange eligibility would have been October 2014. But the lawyers and politicians didn't bother asking the ENGINEERS how long it would take, they never do.
And **THAT**, is my best estimate of what went on and what is going wrong. . .
Well, looking at DC today,, I don't see a lot of difference from "Idiocracy". . . .
Obvious Troll is obvious. . .