Sure, but the purpose of the tech policy office is to
argue why old systems (which have fixed maintenance costs)
should be replaced with new systems which goose the
economy when the federal government pays 10x for what they
should be paying.If and when things break you'll end up with an even bigger disaster if you don't have people prepared to maintain the old systems. A well managed decommissioning and upgrade is much more preferable.
FAA has 45k employees. Around 2% were laid off in 2025 (around 1,600), most of which were new probationary employees or voluntary retirements. They've been hiring since then so the better question is were the subset of people who left the critical factor or some other leadership failure.
In your mind maybe. Most are dead or retired.
New techs have been trained on splicing fiber and VoIP over the last two decades.
Nobody knows about vacuum tubes anymore either, that doesn't mean they were fired and their pensions taken away.
The parts to maintain the legacy infrastructure are no longer manufactured and they are cannibalizing parts for spares.
Not to mention the expertise for these systems have either retired or in some cases passed away.
My grandparents still have a landline and the number of outages in the last 12 months has been insane. Some were in excess of a week.
Many such cases.
For various reasons the team got to a point where lots of the core services were running on totally obsolete technology. I’m talking CoffeeScript here, Python 2.7 there.
Over time, enough turnover and changes happened that they had a pile of repos where not only were the developers on the team unable/uninterested in working on the ancient tech, it was impossible to hire anyone skilled in those areas.
So we ported the features of the legacy services into a modern stack and are STILL working on getting the last of our customers migrated 2 years later. The legacy services are still up but only 2 of us really know a single thing about them, much less re-deploy them if something goes down. Documentation and run-books are great but hands on experience can be really hard to replace in the worst situations
Software environments can more easily be recreated/emulated, especially with VMs being ubiquitous.
With hardware, it's sometimes impossible to recreate. The chips are out of production. The tooling was destroyed and doesn't exist anymore. It's on a whole other level.
https://static.wingify.com/gcp/uploads/abtasty/test-in-produ...
Because if it doesn't work, they call it out for bids
again, select their cronies and get kickbacks. If it does
work, then they've missed an opportunity for grift. Lol. Down-voted by people who work for government
contractors. But apparently they don't downvote people for commenting
on people commenting on downvoting.If you meant to report the user, you have to email [email protected]. They don't bite but they don't always do the thing you wanted.
What about flagging people for using proportional fonts for
attention? Seems vaguely arbitrary.Not only it takes lot of work, but to have the replica connect to the prod in some way to mirror identical behavior will possibly mean adjusting ATO, which is not a simple process in itself.
I'll be interested to see what the root cause of this all is, assuming it doesn't get buried. What I find both perplexing and predictable is how the finger has been pointed at Congress for not funding a replacement. Well, who's controlled Congress for the last 2 years? Who was president in 2017-2021? Who controlled Congress in 2017 and 2018?
If you want to dig deeper, this administration has also (unsuccessfully thus far) claimed in court that they're not bound by Congress when it comes to spending under the Impoundment Control Act.
I watched Sec Duffy's presentation, and it was appalling, but par for the course with this administration: in the middle of a major nationwide outage, he tried to blame someone else.
Even if Duffy got everything he wished for, how do you think they would upgrade a system as old and complicated as ATC. They would have to do it piecemeal anyway. This was a classic upgrade that broke shit. The problem was with the new upgrade, not the old shit that worked.
I do agree with your view.
Over a decade ago I was an intelligence officer and the alarm bells were going off and it was exceptionally clear to the National security community that US infrastructure is barely holding on.
Clapper in 2013:
https://nsarchive.gwu.edu/document/21491-document-90
Dan Coates in 2018:
https://www.euronews.com/2018/07/13/us-intel-chief-warns-of-...
Tip of the iceberg folks. Hold on to your butts…
Both things can be true: US infrastructure is in a dire place AND this monumental acute unforced fuck up is the fault of the unqualified, corrupt people who were put in charge of it
I think the problem with a lot of the push to "modernize" is we forget the legacy system has been real-world tested for 40 years now. It's the new stuff that needs to prove itself in terms of stability.
> if a piece of code (or hardware) has been working without fault in production
But we have tons of legacy code that our engineers don't like, yet it runs fine and has run fine for years.
This thinking caused an extended outage for the biggest mobile network in Australia: https://www.telstra.com.au/exchange/some-mobile-calls-and-da...
Those pair of boxes nobody was brave enough to touch cost them AUD 30 million in fines.
In my mind, anything that's not under continuous maintenance immediately begins to suffer from bit-rot and degrades steadily over time.
Of course, that's not a degradation of digital media, but the "dropping out" of concepts out of people's minds.
This is akin to Netflix's Chaos Monkey approach: systems under constant change and attack necessarily become robust. Systems untouched under glass like something in a museum are typically fragile and crumble if so much as breathed on.
Confidence comes from practice, not ignorance.
Not necessarily. Debugged code is gold.
Sec Mullin: What it appears to be right now is, as Sec Duffy and FAA was going in and putting patches into the system, they were putting new equipment and new technology. And that new equipment and new technology, it was overwhelming the older system. Which is why Sec Duffy made it very clear, the patchwork doesn't work. We need one complete system.