Earlier quoted context omitted.
I think her comment is specifically around software that is critical for human life support. She is advocating for design in such cases. I posted it because I would consider the SW for the F-35 to be in this category. It’s worth questioning whether agile SW development that we do for websites, apps, etc... is good when human life hangs on the line.
Clearly, there was never going to be any way to patch the Apollo Guidance Computer in the middle of a mission. Even if that weren't true, the development cycle was so long that iterative development was never a realistic option. I suspect a project like the F-35 is a hybrid, with elements that are life-or-death mission critical and absolutely need to Just Work, and elements that allow for refinement - even refinement…
The Dysfunctional Trillion-Dollar U.S. Fighter-Jet Program
51–60 of 79 posts
Re: The Dysfunctional Trillion-Dollar U.S. Fighter-Jet Program
#52Will there even be pilots in dogfights in 20 years? Won’t it be mostly autonomous by then? It stands to reason removing the human component would be a far better engineering choice than this monstrosity. I’m reminded of the quote, “A flying car is equally bad at being a car and an aircraft.”
I think you're badly overestimating the speed of development in defense tech. The F-35, a comparatively conventional aircraft, started development 20 years ago and look where it's at. We'd be incredibly lucky to have an even slightly functional one-off prototype of an unmanned fighter 20 years from now.
It’s not inconceivable that one or both of those programs will have an optionally manned fighter in active service in 20 years (2039).
Re: The Dysfunctional Trillion-Dollar U.S. Fighter-Jet Program
#53On an unrelated note: I submitted this article 4 days ago without any discussion [1], does anyone know what the time frame for resubmission on HN nowadays is?
Re: The Dysfunctional Trillion-Dollar U.S. Fighter-Jet Program
#54An interesting angle which is underreported in my view is who is responsible for extremely expensive new military aircrafts: (former) pilots, who are now High-Ranking officers. No pilot has any interest in giving up flying and switching to drones/remote aircraft which are clearly the future. My bet would be that the first country which bets 100% on autonomous aircraft will probably be China, where there will be less…
Re: The Dysfunctional Trillion-Dollar U.S. Fighter-Jet Program
#55An interesting angle which is underreported in my view is who is responsible for extremely expensive new military aircrafts: (former) pilots, who are now High-Ranking officers. No pilot has any interest in giving up flying and switching to drones/remote aircraft which are clearly the future. My bet would be that the first country which bets 100% on autonomous aircraft will probably be China, where there will be less…
The future is drones and so many in the air force know it. Not sure why they haven't bet fully on it. I guess there are no dog fighter drones yet but the first time a supermanuverable <10m drone destroys a 100m manned fighter well it is all over.
Re: The Dysfunctional Trillion-Dollar U.S. Fighter-Jet Program
#56Earlier quoted context omitted.
I think you're badly overestimating the speed of development in defense tech. The F-35, a comparatively conventional aircraft, started development 20 years ago and look where it's at. We'd be incredibly lucky to have an even slightly functional one-off prototype of an unmanned fighter 20 years from now.
All the “sixth gen” or “next gen” programs recently started claim to be optionally manned. E.g the British/Swedish Tempest (introduction planned 2035) and the Dassault/Airbus NGF (also 2035-2040). It’s not inconceivable that one or both of those programs will have an optionally manned fighter in active service in 20 years (2039).
Re: The Dysfunctional Trillion-Dollar U.S. Fighter-Jet Program
#57> There soon turned out to be an essential flaw in the grand plan for a single plane that could do everything. Design specifications demanded by one branch of the military would adversely impact the F-35’s performance in another area. “It turns out when you combine the requirements of the three services, what you end up with is the F-35, which is an aircraft that is in many ways suboptimal for what each of the servic…
Unfortunately, coming up with a design that could effectively fill those roles was more than they could accomplish. Fortunately, the program was cancelled after spending ONLY $6.9 billion.
Re: The Dysfunctional Trillion-Dollar U.S. Fighter-Jet Program
#58> One solution favored by Winter during his recent tenure was so-called agile software development. His vision for “continuous capability development and delivery” resembles DevOps, a popular method in the private sector for quickly testing and evaluating features for new products. Coders generate software upgrades or patches in a matter of days or weeks, pass them along to users to test and then push out the update…
Seems good enough for a general audience.
Re: The Dysfunctional Trillion-Dollar U.S. Fighter-Jet Program
#59Earlier quoted context omitted.
Unless the F35 has a next gen radar which allows it to see enemy aircrafts from farther, it will be bad at dogfights. The point of seeing your enemy from afar is that you launch a missile and avoid the dogfight. It is bad at dogfights http://blogs.reuters.com/great-debate/2014/07/14/pentagons-b...
It's really not. To put it mildly, the report that that article draws from has been subject to some criticism over the years. To put it less mildly, if you link it in any community that follows military aviation closely they will probably make fun of you[1]. Performance is generally better than F-16s in real wold scenarios due to the more powerful F135 engine and the internal weapons bay which means carried weapons d…
Or even a linked drone swarm.
On that basis, the F-35 will be obsolete against the other superpowers by around 2035 at the latest.
Re: The Dysfunctional Trillion-Dollar U.S. Fighter-Jet Program
#60> One solution favored by Winter during his recent tenure was so-called agile software development. His vision for “continuous capability development and delivery” resembles DevOps, a popular method in the private sector for quickly testing and evaluating features for new products. Coders generate software upgrades or patches in a matter of days or weeks, pass them along to users to test and then push out the update…
The comment you point out reminds me of something Margaret Hamilton said: Also, what became apparent with Apollo – though it is not how it worked – is that it is better to define your system up front to minimise errors, rather than producing a bunch of code that then has to be corrected with patches on patches. Source: https://www.theguardian.com/technology/2019/jul/13/margaret-...