I think you need to be more charitable with your interpretation. Sure, "microaggression" is an incredibly loaded term which I don't think is used outside woke intersectionality politics (which, I will declare up front, I think is a terrible thing). However the ability to identify unconscious biases is an important skill — especially in a hard science — regardless of a person's political outlook.

> However the ability to identify unconscious biases is an important skill

I very much agree with that.

But the woke have no interest in exploring that. They already "know" the bias everyone has. It's part of their belief system, and not open for debate or reflection.

Please don't construct a strawman like this. Also, please don't accuse others of doing the same thing you're doing yourself.

p(woke | rationalist) is like pretty high dude

"Is paying attention and acting on microaggressions and unconscious biases"

I understood this as aggresion and bias with regards to work-related technical discussions, for example ignoring or talking over people in a video call who suggest taking a deeper code dive when debugging, or saying "no, I disagree, you are wrong" on a technical point without saying why or making any effort, or starting a call by dropping f-bombs, or shouting "but the code is the documentation!!" when someone politely suggests that issue comments by a library author are also worth paying attention to when trying to understand the meaning of a rabbit's hole of code call chains... especially where these people are from different teams or companies with different incentives.

These are just recent examples of aggression and bias in a technical context that I have personally witnessed.

I agree that fighting the jerk behavior you describe is essential for a healthy team.

It might even be part of what the writer means.

But by using leftist sectarian language they send a strong signal that people like me are not welcome to work in their team.