> Great example! Without context and potentially experience, you might not understand that the helicopter you see upside down in that tree experienced critical mechanical failures, and the pilot saved the lives of himself and the crew by getting it stuck upside down in a tree instead of just crashing into the ground at full speed.
This is everything that's wrong with software today, and I mean that seriously.
What the poster said is "someone fucked up". He didn't say "the pilot fucked up".
If there is a mechanical failure on that helicopter while it's in flight, someone MOST DEFINITELY FUCKED UP. There are processes in place surrounding that helicopter specifically to make sure that pilot never has to make the decision of putting said helicopter upside down in a tree.
In otherwords, someone dun fucked up, and you don't have to be a helicopter pilot or helicopter mechanic, or a helicopter engineer, or anything related to any of it, to be able to identify that someone somewhere fucked up.