So..... this article is making a good point, but it's not following from the presented arguments. It's almost a tautology that unregulated aggression is a bad

So..... this article is making a good point, but it's not following from the presented arguments. It's almost a tautology that unregulated aggression is a bad idea and should be dealt with. but - If you have an idea, how do you know it's a bad idea? That requires critical engagement, taking it apart, putting it back together and performing analysis on it. Doing this well will involve some fairly in-depth reasoning and questioning. If someone is losing their temper in that process, then (1) they are too sensitive/protective and/or (2) someone's being a jerk to the offended party and it's time to knock it off. Egofree programming is an old ideal, but not a bad one. I also retain the mildly heretical notion that a really and truly aggressive environment about code, design, and the quality thereof is probably a more enjoyable place to work than one that focuses on relationships and keeping them smooth. Wrong stuff is wrong, and should be called out and removed. IMO. :) I don't have any comments about gender here, because any gender comment will draw down 'unregulated aggression', and I'm tired of reading such.