Replies

Ancient coding(~1960s) best practices dictate that you never test a brand new system in a production environment. You always, always run the old system and test the new system along side of it to make sure it covers all possible cases and that some unknown bug doesn't bring down the whole system. This is a well known lesson that prevents this kind of thing, yet we saw the same thing with the Obamacare web site roll out. My guess is that too many young people on a project with little practical experience working with actual live systems. It should be a lesson to them that this is exactly how socialism would work with the economy--see Venezuela.

It could also be that because they believe that "diversity is a strength" that they put a bunch of people in charge with no actual experience even completing a coding project, which would lead to total disaster, since the code might not have been tested at all and my not even have been finished on going live day. That would be an even worse failure, because once you go live with incomplete or bad code, the pressure to fix it will burn out everyone and the project will never be done(ie Obamacare web page, they eventually had to take code from someone else to get it working).