I would say it's in between. It's always 100% better to lose an engine in a test where no lives are at risk.
But to compare the loss to how SpaceX loses rockets is not quite the same. SpaceX is built to iterate on it's rockets in a way it can much easier handle a test failure. Blue origin is much more traditional space development where it can actually be much more impactful when a failure happens. See what stevecrox is saying above.
Double whoosh. It's your typo. You called it "Treads" but it's "Threads". Thus the shoe joke (which have treads).
Maybe on re watch just read the synopsis of episodes 1-3 if you've now seen the "boring" ones a few times now as a reminder, then start at 4.
If you are least made it past s1e4 CQB then you gave it a solid shot. That episode imo is where you either pick it up and like it or move on. The first 3 episodes can be a bit slow and introduce so many characters.
A lot of buggy releases often aren't attributed to lack of number of QAs (which helps you find rarer bugs). The simple fact that crazy common bugs any QA probably immediately found and filed, yet was triaged and determined lower priority to other worse bugs the dev team was busy with. Then deemed not stop ship worthy to some exec trying to hit a date.
