On the contrary, I am an experienced systems operations engineer, and know only too well how badly excessive and/or misdirected risk mitigation costs companies.
I have never been accused of being too reckless, however. Developers I've worked with would be happy to relate what a pain in the ass I was about thorough testing and documentation of behavior and risks.
I don't know how to square those statements with reading about a cannonball going through someone's house for no better reason than making a mildly amusing TV show and telling the owners "shit happens".
I'm telling the owners no such thing. I'm telling you shit happens.
The owners will be compensated, and I'm sure there will be measures taken to avoid future incidents of this sort, but your blanket and aggressive condemnation of the actions of the crew are grossly out of touch with reality. Nothing short of absolute safety would satisfy you, and that is simply not possible in real life.
Wow, strawman much? My uneditted words are above, please read them again. I don't see anything "blanket" about saying someone (not "the crew") screwed up badly. Nor do I remember making demands about "absolute safety" beyond saying that the stunt shouldn't have happened where it did (something that even you don't seem to disagree with).
Honestly, you're the one with the half baked, off-the-cuff remark that needs defending. How do you square "shit happens" with "measure will be taken to avoid future incidents of this sort". The latter sounds a lot like you are backpedaling to me.
Your "unedited words": "That stunt should never have happened where it did."
It happened on a military firing range, in the presence of experts. Demanding more is requiring of them essentially perfect foresight. This is equivalent to requiring them to guarantee accidents are impossible.
I do disagree that it "should never have happened where it did", because I reject the notion that causality can be reversed like that. They performed the experiment in a reasonable location for what they knew at the time.
I have never been accused of being too reckless, however. Developers I've worked with would be happy to relate what a pain in the ass I was about thorough testing and documentation of behavior and risks.