It&#x27;s not computer sciences failure it&#x27;s a management issue that stems from a very primitive organizational design of the military.<p>For example, the engineers did not sign off on buggy systems.  The executive officers did because they had a contract with an archaic structure that is not compatible with software development and required the milestone to be met or there be penalities.  But the reason the milestones weren&#x27;t met in the first place was poor management and contract structure created by those executives in the first place.<p>Biggest issue is too much ambition and too much budget trying to be crammed into one project.  Other big issue is lack of closed feedback loops.  It looks like the devs do not have a production system to do integration testing on.  There are probably communication barriers between QA testers ie pilots and devs, caused again by poor structure and culture of military.  Also likely very long lag between releases so few opportunities for iteration.  Also likely using outdated programming languages like C++ for application-level logic.<p>The  nation-state&#x27;s deadly enforcers eg military are directly descended from historical organized crime, since nations generally started as simply the most powerful families.<p>Look at the first premise of this whole thing: we are going to fly around and missile&#x2F;bomb the shit out of you if you don&#x27;t go along with our global domination.  So from the beginning it is poorly planned.