>I'm a mechanical engineer. My point is that stress analysis is the oldest, simplest, and most well understood application of finite element analysis.
And we still get it wrong at times; especially with interactions between disparate parts. See the fatigue problems caused as a result of interactions between the engines and fuselage of the C-133 Cargomaster, or how the F/A-18 had a habit of destroying it's vertical stabilizer due to generated turbulence unaccounted for in the original design. All the FEA in the world gives you a good estimate when you abstract away the details. It doesn't give you the 'real story'.
> I can't even begin to imagine the multiphysics that goes into simulating a nuclear weapon, but if we are willing to bet our entire nuclear deterrent on it, it seems reasonable to skip some additional rounds of physical tests that are mostly a formality at this point.
This is a false equivalence. Nuclear weapons testing has been strictly limited by international accord. You cannot physically test these weapons anymore without "waking up the neighbors" and leading to exceedingly difficult to defuse international scrutiny. That's why the copious levels of "in theory" with regard to nuclear weapons is a reasonable route to take. There is literally no other way to advance the state of the Art. Planes thankfully, don't have that issue. Also, while nuclear weapons testing wasn't restricted, test destinations were done with some degree of regularity; so again, the nuclear weapon point fails.
>Also, defective materials are caught much earlier in the manufacturing process through quality assurance methods, before they become airplanes. And then you apply a factor of safety on your calculations for added assurance.
Just like those leading edge slats for 737 NG, MAX 8 right? You know, the ones that lead to a grounding of aircraft that had already been carrying passengers recently? And who is doing that quality assurance? That bunch of "Quality" people Boeing laid off/relocated elsewhere a few months ago?
Not a credentialed engineer, but know more than enough to LARP as one in certain fields. Testing, aviation/aerodynamics, mechanics of materials, and software being some of them.
You simply cannot know what you're dealing with until you actually test it, and it's generally right after you stop doing that one test that just tells you exactly what you think it should that you get that design with a problem that would have manifested if you just did it.
The only people who should be interested in decreasing testing is the sales, accounting, and business departments. As Engineers, we've had upward of 100 years of design driven 'oopsie' to grind into us the fact we are, in fact, not as clever at accounting for the real world as we think we are.
The fact that as a credentialed mechanical engineer, you don't see it this way is concerning. Though again, I've not had my scrutinous edges rounded off by regular business constrained application either. So there is that.