Point number 1 is ridiculous and sexist.
Oh yeah let's ship code that hasn't been reviewed because the young males in our company will act like chimpanzees, and those pesky technical debates let's scratch those too. Let's just use whatever piece of technology is trending today on HN
No one's saying we shouldn't have code reviews or technical debates, just that we need to avoid being overly aggressive. A lot of young males (including myself previously, and sometimes currently) can be very aggressive in presenting their views. This disenfranchises less outspoken people in our teams, particularly woman who generally can't be as aggressive without negative social ramifications.
I didn't say "no code reviews" I said aggressive. I've personally seen a world a difference in response from (mostly) young female engineers when the review is less about "you did this and this WRONG, FIX IT" than talking through design decisions calmly and without the (passive) aggressive stuff.
Yes this can apply to males too, but my empirical observation is mostly more applicable to females.
I didn't read that as suggesting that you shouldn't do code reviews.
The issue is when code reviews become a competitive sport, and more about technical oneupmanship than they are about improving code quality and team knowledge.
The entire purpose of a code review is to highlight things that are wrong. You can't point out things that are wrong without someone being able to spin your comments as some kind of toxic masculine impulse to show basal-primate technical dominance through demonstration of superior shamanistic technical knowledge.
Get a fucking grip. Pointing out a buffer overflow isn't sexism. It's pointing out a fucking buffer overflow.
You could have communicated your point without the aggression. That's what I presume is gedy's original point.
> You can't point out things that are wrong without someone being able to spin your comments as some kind of toxic masculine impulse to show basal-primate technical dominance through demonstration of superior shamanistic technical knowledge.
Who hurt you? I suggest you find greener pastures if you truly believe that.
Come on, you know as well as I do that there's a large chunk of (mostly male, frequently young) who LOVE to point out how wrong someone it to show how wrong someone else is. Whether it's aggressive or just passive aggressive there alternative ways to be polite and not off-putting to those less aggressive.
Pointing out things that are wrong is fine. If you're incapable of doing that without being rude or condescending then code reviews aren't going to be the only place your lack of social graces hinders you.
