undefined | Better HN

0 pointsthrowaway1119994y ago0 comments

> No offense but this is such a silly thing to say. EVERYONE sees race/age/sex.

I strongly disagree here. When I'm reviewing code, I look at the code. It could be written by ANYONE. I don't ever think "this woman" or "this <religion>" when reviewing code!

> "I like those earrings, they look great" - no problem. > "Hey I really like the way that shirt fits your body" - problem

You don't see how it can be easy to accidentally state the latter? If you don't... I just don't know what else to say. A major part of fashion is accentuating or hiding parts of someone's body...

In any case, as I said, I acknowledge that it's an irrational fear and I'd just rather not take the risk.

I think your main POV here is that if your heart is in the right place then everything will be fine. I just hard disagree with that.

> And my point is that you're saying you are knowingly and intentionally treating your female coworkers significantly different than your male coworkers, and that's kind of weird, and will likely lead to more issues than if you just treat them the same...

No, I treat them both equally but I avoid expressing any opinion whatsoever becomes I'm worried about being perceived otherwise.

I don't give female coworkers critical reviews, but I don't give male coworkers bad reviews either.

What I'm saying is that I very strategically avoid ANY situation where my I can express an opinion that MAY be perceived as "-ist".

In other words, think of any situation where intent is a major factor.

Example: A very veeerrrry nit picky code review. Some people are nit picky about every single thing to every single person. That's fine. But if someone is nit picky ONLY to female coworkers then that's a problem.

Intent is what matters there. My (again, irrational) fear is that my intent my get mis-read due to bad luck. My code reviews can be inconsistent sometimes. Some days I might point something out that I wouldn't on other days. Just human error. See what I mean?

0 comments

tw044y ago

>I strongly disagree here. When I'm reviewing code, I look at the code. It could be written by ANYONE. I don't ever think "this woman" or "this <religion>" when reviewing code!

But that's not what you said. And it's not really the point either way, because we're talking about providing feedback on the code, which was written by a person with an age and a race and a gender. And when you sit down with that person to provide feedback, you see their race, age, and gender. Saying you don't is just silly.

>You don't see how it can be easy to accidentally state the latter?

I really don't.

>I think your main POV here is that if your heart is in the right place then everything will be fine. I just hard disagree with that.

I don't think and didn't state that at all and would never give anyone such absurd advice. I could go on with more examples for you:

I really like those shoes. - perfectly fine

Those shoes make your legs look great. - don't do this

That skirt is cute. - Yes

That skirt makes your butt look amazing - don't do this

I honestly can't tell if you created the throwaway for entertainment or having a real conversation but at this point I'm leaning towards the former because I genuinely don't believe you're confused about how to make an appropriate vs. inappropriate comment to a coworker. It doesn't really matter if they're male or female, if you tell someone that an outfit makes their body look X - you're probably going to get in trouble unless you happen to be good friends outside of work.

>No, I treat them both equally but I avoid expressing any opinion whatsoever becomes I'm worried about being perceived otherwise.

It doesn't really matter how you're perceived. If you document your reviews, and you do it fairly, the work will speak for itself. It has nothing to do with male vs. female. I've done this for decades, someone will inevitably accuse you of a bias, and you refer back to your documentation, notes, and the original work. They can mis-read all they want, the only thing HR cares about is a defensible position for your feedback.

throwaway111999OP4y ago

> But that's not what you said. And it's not really the point either way, because we're talking about providing feedback on the code, which was written by a person with an age and a race and a gender. And when you sit down with that person to provide feedback, you see their race, age, and gender. Saying you don't is just silly.

Maybe you and I mean different things when we say "see age/etc". Yours is probably more correct semantically, but when I say "see" I mean specifically adjusting my code review depending on age/etc. When I say I don't "see age/etc" I just mean that it doesn't influence how I evaluate someone's work professionally.

> I honestly can't tell if you created the throwaway for entertainment or having a real conversation but at this point I'm leaning towards the former because I genuinely don't believe you're confused about how to make an appropriate vs. inappropriate comment to a coworker. It doesn't really matter if they're male or female, if you tell someone that an outfit makes their body look X - you're probably going to get in trouble unless you happen to be good friends outside of work.

Your mildly toxic responses are a great reason why I don't engage on this subject matter at all (until now). And the reason why I created a throwaway account.

You seem to be very sure about yourself and how everyone else should act. You also seem to lack any compassion by default for what people struggle with. Honestly, your responses have even further convinced me that my approach is the correct one (for my own good/safety/etc).

My comment was me genuinely opening up. It's something I struggle with internally. If you work with me, you'd never know it.

> It doesn't really matter how you're perceived. If you document your reviews, and you do it fairly, the work will speak for itself. It has nothing to do with male vs. female. I've done this for decades, someone will inevitably accuse you of a bias, and you refer back to your documentation, notes, and the original work. They can mis-read all they want, the only thing HR cares about is a defensible position for your feedback.

Or I can just not engage at all. What do I stand to gain from having to deal with documentation/notes/etc in those cases? In environments where critical feedback is encouraged (or even required) then all I need to do is be less critical than the most critical people. Or in other words, only provide feedback that someone else has provided in the past.

j / k navigate · click thread line to collapse