SpaceX’s entire development philosophy is “test early, test often and learn from failures”. This is a much quicker pace than simulating every imaginable failure scenario and leads to faster progress in development.
This is a catchy statement, not an actionable philosophy. There’s many ways to do it, and it’s entirely possible that SpaceX is doing it poorly.
There’s a lot of value in brainstorming every imaginable failure scenario. It’s industry standard to do so in fact with HAZOPs. There’s failures that you may not necessarily see in testing – especially those that are rare but catastrophic. This is a field that should be acutely aware of that given past events.
There’s also a right way to do testing and a wrong way to do testing. You typically consolidate tests and do several at a time, depending on the stage in the project. And you don’t typically risk precious equipment in doing so.
Bimfred@lemmy.world 5 months ago
There’s a point at which you learn more from actually building something and putting it through its paces than simulating. It’s a tough balance to strike , no argument there. Simulating until you’ve covered every conceivable edge case and failure mode is ludicrously costly and time consuming. Relying entirely on yeeting shit and seeing how it fails risks missing the edge cases. But so far, I’ve seen little reason to doubt that SpaceX has found a working balance between simulation and practical testing. They’re certainly progressing faster than the industry historically has and the F9 has had no failures, even partial ones, in over 200 flights. That’s a track record that most launch vehicles can’t meet. It’s definitely possible there’s a 1/1000 flaw in the Falcon 9, but until it actually happens and they lose a rocket and/or a payload (gods willing it won’t be crew), it’s nothing but a hypothetical “but what if…” scenario.