On 10/28/2013 5:55 PM, Califbill wrote:
Charlemagne wrote:
On 10/28/2013 1:24 PM, Califbill wrote:
Charlemagne wrote:
On 10/28/2013 12:35 PM, Califbill wrote:
Hank© wrote:
On 10/28/2013 7:50 AM, F.O.A.D. wrote:
On 10/28/13, 7:34 AM, iBoaterer wrote:
In article , says...

On 10/27/2013 3:13 PM, F.O.A.D. wrote:
Let?s see?

$350 million or so spent on health insurance exchange spftware that
isn't working properly yet and the Republicans are losing their minds.
But?$400 Billion spent on the F-35 Joint Strike Fighter that doesn?t
work and no one seems to need, and the Republicans don?t say a word.

HUGE difference. Developing and prototyping a Military Fighter is
nothing like writing a simple database... especially when you consider
most if not all of the code is out there already, just needs to be
compiled... A very dedicated high school student could probably write
the site as a senior project in a couple semesters....

snerk



If you look at PsychoSnotty's "iDesign" pages, you'll think a junior
high school designed and programmed them.

How do we know that Harry Krause could do any better than a junior high
school designer/programmer?

---
This email is free from viruses and malware because avast! Antivirus
protection is active.
http://www.avast.com

These days, probably not as well. Kids these days never seem to come
outdoors and play, so they must be doing a lot of compute ring.


Our public website is a billboard... Most of the hard core "design" we
did in the past revolved around making different systems and languages
"talk" to each other...

Here's the deal.. I will stipulate that "one week and ten grand" was a
wild exaggeration for effect, but I made my point. If you understand that
most of the problem with the ACA website was that too many different
companies "shared the wealth".. (Probably half the money went to the
paperwork you need to fill out to write a website for a local college for
**** sake....) The problem was, too many companies, with different
operating proceedures and structures for building a site, it was a case
of "too many cooks spoil the broth". If one company had taken a team and
written the thing, I still submit it could be done for a million or
two.... probably less...

You just have to get by the source here, and look at the facts... The
fact is, the project was so splintered, it never stood a chance...

Just lease the software from a company that has already written and
debugged the software. Writing the software could maybe done for a
million, but the testing and verification would take a lot more money and
time. Was a problem with UNIX for years. Lots of the drivers were written
as college papers. They did not handle exceptions well, if at all. Those
are harder to test.


Yes, verification is really the hardest part we ever faced taking
input... Either way, you have 50 companies in on this that don't
necessarily talk to each other...

Did you even have a written Design and Verification plan? Part of my
career was bioengineers devices, and we damn sure had written plans. We
had to submit them as part of the approval process to the FDA. Should be a
written plan for ACA website also.


We had to do a lot of different paperwork when we were contracted to the
State College... Lot's of federal hoops to jump through. Every contract
was different. The huge one we did for Prudential, our "design and
verification plan" was a working module. We had to write it to sell it,
it was a huge risk for sure....