> Wow, way to go! I read HN so I must be a PG cheerleader and ergo I'm definitely sexist!
For someone who is all about psychological errors, you seem to have constructed quite a narrative. I'm not talking about cheerleading -- just the level of analysis. I'm not trying to make you into some horrible monster or anything -- that is your projection onto my criticism.
Speaking of psychological blinders: I stand by my assertion that, as long as anyone doesn't mess with your ego, you will not apply this level of analysis to what they write. It's human nature. At the risk of repeating myself, I just don't think you're reading PG's articles and thinking that what he says happened to him, didn't happen.
> Should anyone be able to wear anything to any job without any consequence?
Oh come on. Really? RTFA. You're veering away from the misattribution you original claimed as a possibility here.
I just wrote a whole comment about context, and you ignored it because it bruised your ego. Being obstinate about "drawing a line" is not a triumph of reason -- it's ignoring the world. Reductio ad absurdum relies on symmetry, of which you have none here.
She's obviously not wearing hot pants, a bikini top to work, and even if that were the case, she would be notified in an official capacity in short order (e.g. "told to go home") -- not "complimented" repeatedly in a creepy way.
There is no "murky line" because we are talking about a repeated pattern she illustrates in her article which shows it highly likely not to be misinterpretation. If she misinterpreted one of those examples (e.g. the "Facebook" example is the one I'd choose, actually), ok. But how likely is it she misinterpreted all of them, and the misinterpreted the social environment that made her pull together the examples in the first place?
> Please realize that there's a difference between saying "it might not be sexism" and "it's definitely not sexism" and that I'm trying to very cautiously propose the former, not the latter.
If I have a bug, it might be cosmic rays, a compiler bug -- or it could be my shitty code. All of these are possible. It isn't about what's possible, if you want to be analytical about it.. it's the likelihood.
So, when you say "it might be a compiler bug" when code breaks, you should know how ridiculous that sounds, even though you are technically correct[1]. There is a reason people say those kinds of things (without much more evidence) and it has a lot to do with how attached they are to their code.
[1] The Best Kind of Correct.