4 ms·

Keep in mind that if I am in a team of 5, then 80% of the group is in the dominant "not-me group" and 20% is in the minority "me group". We often (and reasonab

Keep in mind that if I am in a team of 5, then 80% of the group is in the dominant "not-me group" and 20% is in the minority "me group". We often (and reasonably) choose to prioritise the needs of the dominant group over the non-dominant group. If I want to use Elm, but the rest of the team wants to use JS and React, I'd actually be a bit of a jerk to force them all to accommodate my wishes. While contrived, I'm convinced this is precisely the problem. If I am a woman on a team of men, am I a bit of a jerk for demanding that the rest of the team accommodates me? Perhaps they all have a communication style that suits them that is born from their upbringing as male children while I have a communication style that equally suits me, but is different from theirs. Must I adapt to their system, or should they adapt to mine? When we talk about programming style, or preferences for tools the answer is seemingly easy. We go with the majority so that we please the most people. When we talk about gender, sexual orientation, race, etc the answer is much more complex. We can divide our groups in infinite ways and yet some categorisations are chosen to be significant while others are not. Because of this, I feel that it is actually really important that we recognise that we will not and can not accommodate everyone. Being different, having a different opinion, having a different set of experiences is not actually enough to warrant special treatment. In many cases we choose to discriminate: no matter how good a Java programmer you are, we will not write our frontend in GWT! (Real story: I maintain a frontend written in Java and GWT, so I'm taking some liberties ;-) ). As I said, there are some special cases where we have decided that we wish to provide special accommodation. We do this because, on balance, we believe that doing so enriches our societies. It will always be a tradeoff, though, and it's important to understand that. Consider the word "discrimination". Without that word, we can not discriminate between "good" and "bad". We do not want to live in a world without discrimination. We should always strive to discriminate in such a way as it makes the world a better place. We wish to avoid behaviour that works against our interests and encourage behaviour that works for our interests. To that end, we specifically discriminate in certain situations so that we accommodate minority groups in a way that we feel enhances our society. It should not be a surprise if we occasionally get this wrong and I strongly discourage people from assuming that the "right" answer is easy to determine. It is important that we think very carefully about which things we wish accommodate (minority representation of gender, sexual orientation, race) and things which we do not wish to accommodate (hate speech, violent behaviour, and GWT :-D). P.S. I hereby apologise for my horrible characterisation of Java and GWT. I actually don't mind it that much...

sfink 7y ago
Valid points. I have used the example of a lone vegetarian joining a team with a tradition of eating together at a steak house. In my mind, it would be a reasonable accommodation to stop doing that once a vegetarian is hired -- low cost to switch, highly obnoxious not to. I find your example of communication style to be trickier. It feels in-between to me. I would agree that some elements of communication style should not be changed to accommodate an inflexible newcomer. On the other hand, when people talk about the benefits of diversity, communication style is a really large element! You know what you enjoy about your current boys' club style -- but it might very well be better if you switched to something more professional even in the absence of onboarding someone new. You won't know until forced to by the introduction of diversity, and that's true in many different subtle areas, not all of which you're going to have any chance of spotting in advance. The same argument could be applied to just about anything. Perhaps GWT would be a really great fit for what you're working on, but you won't know until you try it. That's far less likely than a communication style change, though, so it's probably one of the costlier and less likely things to try to accommodate. I agree that the question of whether or not to accommodate a difference is not always answered with "yes!" It depends on the accommodation required.

sfink 7y ago

Valid points. I have used the example of a lone vegetarian joining a team with a tradition of eating together at a steak house. In my mind, it would be a reasonable accommodation to stop doing that once a vegetarian is hired -- low cost to switch, highly obnoxious not to. I find your example of communication style to be trickier. It feels in-between to me. I would agree that some elements of communication style should not be changed to accommodate an inflexible newcomer. On the other hand, when people talk about the benefits of diversity, communication style is a really large element! You know what you enjoy about your current boys' club style -- but it might very well be better if you switched to something more professional even in the absence of onboarding someone new. You won't know until forced to by the introduction of diversity, and that's true in many different subtle areas, not all of which you're going to have any chance of spotting in advance. The same argument could be applied to just about anything. Perhaps GWT would be a really great fit for what you're working on, but you won't know until you try it. That's far less likely than a communication style change, though, so it's probably one of the costlier and less likely things to try to accommodate. I agree that the question of whether or not to accommodate a difference is not always answered with "yes!" It depends on the accommodation required.