Earlier quoted context omitted.
These contracts are generally bloated, but if you've never seen how a $10M+ contract for things like this works you're probably thinking about it wrong. The actual development piece is a pretty small portion of the overall work. The bulk of it is figuring out all the requirements, wrangling legacy systems and data into some kind of shape that can either be interfaced with or imported, documentation, support (includin…
When did we have the last nationwide vaccination campaign, whats the "legacy"? Pretty sure that was when IBM still made tabulators. I think you will find that if only there was someone in charge to put their foot down, you can do without a whole lot of these things. But that's part of the problem of course: the government contracting out is just a bunch of clueless people making up a wish list with a partner on the o…
CDC website built by Deloitte at a cost of $44M is abandoned due to bugs
131–140 of 688 posts
Re: CDC website built by Deloitte at a cost of $44M is abandoned due to bugs
#132I just don't understand these software deals, the price is so high. At 44 million, you can hire 146 engineers each paid 300k for a full year. Trust me, you need much less to build something like this, and there's no excuse for it to suck so bad. I'm also curious, anyone know where the development actually happened? Did Deloitte further subcontracted out? Was it outsourced?
If you want to see another ultimate example of this sort of contracting gone awry, google "canada federal payroll phoenix system" https://www.google.com/search?client=firefox-b-d&q=canada+fe... example news URL: https://www.itworldcanada.com/article/phoenix-payroll-system...
Re: CDC website built by Deloitte at a cost of $44M is abandoned due to bugs
#133I just don't understand these software deals, the price is so high. At 44 million, you can hire 146 engineers each paid 300k for a full year. Trust me, you need much less to build something like this, and there's no excuse for it to suck so bad. I'm also curious, anyone know where the development actually happened? Did Deloitte further subcontracted out? Was it outsourced?
The worst part is that we know government software contracts are done completely wrong but the government doesn't want to change. Too much money to be made.
Re: CDC website built by Deloitte at a cost of $44M is abandoned due to bugs
#134The last time the US government made something to be proud of was 50 years ago with the Apollo program. Counter examples welcome!
https://en.wikipedia.org/wiki/Internet_protocol_suite
To be fair... it's also from about 50 years ago. Hmm...
Re: CDC website built by Deloitte at a cost of $44M is abandoned due to bugs
#135The last time the US government made something to be proud of was 50 years ago with the Apollo program. Counter examples welcome!
The Hubble Space Telescope? (and the other "Great Observatories" satellites)
Meh.
Re: CDC website built by Deloitte at a cost of $44M is abandoned due to bugs
#136Earlier quoted context omitted.
When did we have the last nationwide vaccination campaign, whats the "legacy"? Pretty sure that was when IBM still made tabulators. I think you will find that if only there was someone in charge to put their foot down, you can do without a whole lot of these things. But that's part of the problem of course: the government contracting out is just a bunch of clueless people making up a wish list with a partner on the o…
The data flows into legacy systems like VAERS
So now what, you are reporting this adverse event to VAMS who reports it to VAERS? There is no flow, it's all just duplicate effort from architecture astronauts.
Re: CDC website built by Deloitte at a cost of $44M is abandoned due to bugs
#137> Why was Deloitte awarded the project on a no-bid basis? The contracts claim the company was the only “responsible source”[1] to build the tool. [1]: https://www.acquisition.gov/far/6.302-1
Re: CDC website built by Deloitte at a cost of $44M is abandoned due to bugs
#138Earlier quoted context omitted.
This is not a 'software engineering' thing. If you look at it from a software development POV, then the issue is more of not having 'product managers' whose job it is to - understand the requirements, write the specs, basically champion the POV of the end user (after actually identifying the correct end user). Examples a) The article talked about the software not working on Internet Explorer (IE). Older people still…
Internet Explorer has less than a 2% market share in the US, so under normal circumstances (given the sacrifices you’d have to make everywhere else) not bothering to support is is often a sensible decision. When it’s an access to healthcare issue though you can’t really exclude 2% of users. That said, building something that works well on mobile (re your point b) but also works on internet explorer is a pretty tough…
Re: CDC website built by Deloitte at a cost of $44M is abandoned due to bugs
#139I just don't understand these software deals, the price is so high. At 44 million, you can hire 146 engineers each paid 300k for a full year. Trust me, you need much less to build something like this, and there's no excuse for it to suck so bad. I'm also curious, anyone know where the development actually happened? Did Deloitte further subcontracted out? Was it outsourced?
Full disclosure: I have had the distinct "privilege" on having worked with all aspects of large consulting firms, from working at Cap Gemini, to being a sub for a smaller company on a large gov't contract with Lockheed Martin, to actually competing (and winning) against the large companies with my own, small consulting company startup. In short, the above comment is spot on. Companies like Deloitte, Cap Gemini, PwC,…
Re: CDC website built by Deloitte at a cost of $44M is abandoned due to bugs
#140Earlier quoted context omitted.
This is not a 'software engineering' thing. If you look at it from a software development POV, then the issue is more of not having 'product managers' whose job it is to - understand the requirements, write the specs, basically champion the POV of the end user (after actually identifying the correct end user). Examples a) The article talked about the software not working on Internet Explorer (IE). Older people still…
Internet Explorer has less than a 2% market share in the US, so under normal circumstances (given the sacrifices you’d have to make everywhere else) not bothering to support is is often a sensible decision. When it’s an access to healthcare issue though you can’t really exclude 2% of users. That said, building something that works well on mobile (re your point b) but also works on internet explorer is a pretty tough…
Why isn’t this just the site?
I love Spartan, ugly, functional sites. That’s what the government should build, always. They should have style guidelines that are basically “no style”.
You’re not competing with anyone, there’s no need to look good. Function, function, function.