>("Getting the job done" does not, and has never required being abusive to others. Getting the job done while being abusive is not proof that being abusive is required or even was part of, "getting the job done.")
Hmmm.. I'm going to disagree here. Being verbally abusive is a technique to demand change in an organization. We all like to think leaders all command respect and everyone just follows them because they're the leader. Bullshit. One technique, employed by MANY leaders is being a total fucking asshole, at least part of the time. You think anyone would be talking about this GCC bullshit (and if what Torvalds says is right, it's really completely fucked up, and not excusable) if Linus just put a nice, politely worded request to just fix shit? I don't think so. But even if he was nice and polite, and got the thing fixed, there's little or no consequence for the fuckup, so it can happen again. If you're coding GCC, maybe you might at least sub-consciously think "boy, I better not release utter shit, or I'll catch some serious shit from that asshole Linus Torvalds... what a cock gobbling asshole that Torvalds is".
This idea you have that everything can work in a nice polite society where everyone has mutual respect for each other can work sometimes, in limited capacities. But the norm is for assholes like Linus to sometimes throw shit-fits, and others to work in fear of having a shit-fit thrown at them sometimes.
Is that the ONLY way to run an organization? Probably not, but as another thread points out, it's a common pattern of effective leaders.