Please register to participate in our discussions with 2 million other members - it's free and quick! Some forums can only be seen by registered members. After you create your account, you'll be able to customize options and access all our 15,000 new posts/day with fewer ads.
Hard to understand that large projects fail regularly. I know. I couldn't understand how the companies I worked for could LITERALLY blow 250 million on something that was fubared from day 1. And yet I saw it multiple times.
Good salespeople, bad management, and cost plus accounting. Basically how every single government program works. And even a lot of corporate ones. Its mind boggling.
Take a look at every single military program. Lets pick the F35 for example (although there are many many worse examples). Literally doubled in price. From a 200 billion dollar program to a 400 billion dollar program. I think the F-22 and the new navy ships have done worse. Know whats even worse? The F-35 has had the companies involved freaking out because under new rules the government has pulled some money from them reducing their profits. (While its the Obama administration doing this, I think the rules were created under Bush, not sure)
Cancelled programs? The army and navys got them in spades.
Welcome to reality. Big programs fail....software ones have an amazing failure rate. And being in the industry its very depressing to work on something you know is going to fail.
Heck, I have friends that work for Nike and will spend months working on an expensive project only to have upper management ditch the idea to move onto something, basically turning all that work into garbage.
Yes I do actually. Probably better then the vast majority of people here. I both live in Oregon, AND work as a software engineer-with experience on large scale medical software in the past
I once was the systems administrator in charge of creating and putting together a HIPAA compliant software package for an insurance company and thought the $1M price tag was out of line..
To even equate this to the $1B+ price tag for a web interface has me astounded that anyone is defending them.
Heck, I have friends that work for Nike and will spend months working on an expensive project only to have upper management ditch the idea to move onto something, basically turning all that work into garbage.
We have similar stories but that would mean that the projects they were working on was a failure and ill conceived while you continue to support policies which fit that definition nicely.
I once was the systems administrator in charge of creating and putting together a HIPAA compliant software package for an insurance company and thought the $1M price tag was out of line..
To even equate this to the $1B+ price tag for a web interface has me astounded that anyone is defending them.
Its not JUST a web interface-theres actually a ton of stuff thats supposed to occur under the hood with lots of separately controlled databases.
Its not JUST a web interface-theres actually a ton of stuff thats supposed to occur under the hood with lots of separately controlled databases.
Yeah, Oregon took a big risk. This site was suppose to be an all encompassing system. I remember reading about it when they first started and it could have been a really impressive system, unfortunately it was poorly handled by the company it was given to.
Its not JUST a web interface-theres actually a ton of stuff thats supposed to occur under the hood with lots of separately controlled databases.
I dont give a rats ass how many databases it has to interface with, its code, and code and select code is the same if you are connecting to one database, or multiple. The only difference is the prefix.
Select * from database1.insurance doesnt cost any different than Select * from database2.insurance
Yeah, Oregon took a big risk. This site was suppose to be an all encompassing system. I remember reading about it when they first started and it could have been a really impressive system, unfortunately it was poorly handled by the company it was given to.
So the state bears no responsibility because it contracted it out? Perhaps they should've given it to a more competent company.
So the state bears no responsibility because it contracted it out? Perhaps they should've given it to a more competent company.
Funny watching the same people who defended the federal contractors moan and groan about state contractors
Please register to post and access all features of our very popular forum. It is free and quick. Over $68,000 in prizes has already been given out to active posters on our forum. Additional giveaways are planned.
Detailed information about all U.S. cities, counties, and zip codes on our site: City-data.com.
Please register to participate in our discussions with 2 million other members - it's free and quick! Some forums can only be seen by registered members. After you create your account, you'll be able to customize options and access all our 15,000 new posts/day with fewer ads.
