A corrupt file led to the FAA ground stoppage. It was also found in the backup

Re:A corrupt file led to the FAA ground stoppage. It was als... by JCM9 on Thursday January 12, 2023 @09:47AM (#34354218)

I hear you. But the flip side is there is often a tendency to massively over complicate things in a way that bakes in valueless complexity and bloat, which is very much the norm in large government systems. I’m practice this attitude is far more common and destructive long term.

[ Parent | on HN ]

Re:A corrupt file led to the FAA ground stoppage. It was als... by nonethewiser on Thursday January 12, 2023 @10:01AM (#34354464)

I think it's way worse than adding complexity and bloat. There are processes that specifically prevent anyone from understanding or owning the system. The complexity and bloat is a side product of the fact that the work was siloedd, contracted out, and everyone washed their hands off the result. Which also takes exponentially more time and people.

Its optimized for inefficiency.

[ Parent | on HN ]

Re:A corrupt file led to the FAA ground stoppage. It was als... by gnarbarian on Thursday January 12, 2023 @10:56AM (#34355423)

this is extremely accurate. it's like a giant rube Goldberg machine that takes both good code and garbage as input and produces a tremendous amount of garbage that nobody can understand once it comes out the other end.

[ Parent | on HN ]

Re:A corrupt file led to the FAA ground stoppage. It was als... by bink on Thursday January 12, 2023 @12:11PM (#34356926)

Do you know that each of these systems actually has a defined "owner"? It's part of the FISMA process and every so often these "owners" have to attest that certain security processes are in place and functioning and that no significant changes have been made without a full review... among many other things.

That "owner" is also a federal employee, not a contractor.

https://en.wikipedia.org/wiki/Federal_Information_Security_M...

[ Parent | on HN ]