I think a lot of people miss the fact that SpaceX engineers know very well that what they're doing might fail spectacularly, and that this is the cost of speed.
A random example: autogenous pressurization.
It's beneficial to have a rocket's engines pressurize the tanks themselves rather than to haul up pressurant tanks and a separate pressurant. But it's surprisingly tricky. For a methalox rocket, you ideally want hot methane injected into the methane tank, and hot oxygen into the oxygen tank. But hot oxygen is very difficult to work with in an engine, as it tends to eat your engine.
If you're still working on reliably producing hot oxygen, there is a hack available to you, but it's not pretty: just inject exhaust into the oxygen tank; after all, it's not combustible. BUT, it is water and carbon dioxide. Both can settle out as frosts or plated ices, and in the liquid, the water ice will float at the top, while the CO2 will form a snow at the bottom. Frosts / ice plating can block e.g. your RCS jets. The CO2 snow will kill your engines. You can put in filters around their intakes, but it'll clog your filters. You might try expanding the filters, and maybe that'll work for a while, but then you rotate the rocket, the snow rushes ti one side, and a bunch of engines die from clogging. You may put some big mesh plates across the whole tank to keep the snow off the bottom, but they can cause their own problems with fluid flow and still sometimes clog or let snow through during maneuvers. Etc.
So then comes the question: put Starship on hold while working on getting the engines to reliably produce hot oxygen, potentially for years, or forge ahead with a hack solution that you know has a reasonable chance of killing your rocket?
To SpaceX, the question is obvious. You cannot afford to give up years of critical flight data just to avoid some booms. The decision is immensely lopsided in favour of "put in the hack solutions and launch, while you work on the proper solutions". Because you learn SO much from every launch that can be used to evolve your design. And you also learn so much from every rocket that you build, whether you launch it or not, so you might as well launch it.
To be clear, you don't want to lose rockets due to doing stupid things. Like, for example, if it turns out that some SpaceX engineer installed the wrong COPV and caused the recent pad explosion**, basically the only thing they would learn from that is "have tighter controls on your COPV processes", which isn't at all worth the cost of the explosion. But in general, if you launch and it clears the pad, you're getting good, important data from it, it's worth it even if it blows up seconds later, and it's on to the next evolved version of the rocket in your production sequence with both production- and flight lessons learned.
** It's clear that the recent explosion was from a COPV failure, but it's unclear why. Some claimed leaks state that a COPV may have been coded to a higher pressure than it actually was during production, so when they scanned it it checked out as being the right tank, but actually was not designed to handle the needed pressures. But I'll wait for official confirmation on this. SpaceX only makes some of their COPVs, usually not the smaller ones - ones that have washed up ashore were made by Luxfer. So this could be a supplier problem, like the strut failure on a 2015 Falcon flight. But again, too early to say.