And they failed at that too. Apparently what would have been a weekend project for a high school student was so hard for a federal agency that they burned $3.1 billion trying to do it. (This level of incompetence is truly despicable.)
I wonder if there is something pathologically wrong with government and how government (at least in the U.S.) does spending.
I just think it’s a shame that it’s politicized because we can’t easily discuss it as a case study without pre-existing political opinions creeping in. It would be neat if this particular series of events could be dissected in a vacuum. Government projects go sideways all the time but there’s a lot of transparency into why this one did because of the unique circumstances of its resolution.
Both sides of the aisle have patrons that feed at this trough and I doubt we'll ever get consensus better operational insights and less waste and fraud.
Like so many other issues, the only thing holding us back from achieving this is will.
People should be free to vote for someone that best represents them, without worrying about a spoiler effect or strategic voting practices.
There's plenty of input to consider on how to improve things, we just need to find the collective will to act on it.
https://www.brookings.edu/articles/reforming-federal-procure...
It's estimated that US healthcare per-capita spending is 20% more than countries who use a single-payer program (that's nearly every other developed country in the world).
> Testing was largely a manual process. Releases and deployment required lengthy overnight downtimes and often failed, required equally-lengthy rollbacks. The core data layer lacked a schema. Provisioning hosting resources was slow and not automated. Critically, there was a pervasive lack of monitoring of the site. No APM, no bog-standard metrics about CPU, memory, disk, network, etc., that could be viewed by anyone on the team.
If you know how to do it without being indicted anyway.
Constant back and forth change orders, pointless delays to serve constantly changing stakeholders, constant demos with no real product, no one in the customer with any power who has experience to call BS on timelines or delivery, etc.
And if done correctly, everyone in the ‘customer’ is simultaneously happy and angry and so it’s easy to deflect blame and point fingers back into their own org.
Or so I’ve heard from folks who are involved. I try to avoid it like a plague, the BS I deal with hurts my soul enough already.
The federal government is a big beast, though, so it takes a while for the idea to spread.
If leadership isn't careful (and it seldom pays to be careful), it becomes an excuse for every real wrong.