My understanding of this is that black people have no access to education to become a developer and start caring about this. Also those who do that I could see expressing themselves on the topic say that they "don't give a fuck".
And definitely the racism around us is invisible because it is a part of normality and to be able to change it we're going to need to make deep changes. But the answer is there, deep changes. If you start with the sand there is no space for the big rock.
Let's take the problem in another way, with a lack of systemic oppression, would it still be a problem to have a concept of master/slave? Or just master in this case. It describes very accurately the technical concept. My ancestors were definitely salves to some Roman dude and in no way do I get hurt by the term.
Overall, I have no fundamental problem with using another name for the Git branch or describing my architecture another way, however it's like cleaning up your room instead of doing your homework: you're getting a sense of accomplishment for doing not so much.
And my fear is that a lot of the white people racing to ban "master" from their vocabulary are going to stop at this very effort because they feel they've done their part but this won't prevent them from shit-talking the Indian offshore team.
So yes, action often ends at acknowledgement and virtue signalling but this is the least bit that can be done to make work culture more inclusive. And uh, even if there are less people of colour (esp dark skinned folks) in tech doesnt mean they don't exist...
Some comments have been hidden by the post's author - find out more
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
My understanding of this is that black people have no access to education to become a developer and start caring about this. Also those who do that I could see expressing themselves on the topic say that they "don't give a fuck".
And definitely the racism around us is invisible because it is a part of normality and to be able to change it we're going to need to make deep changes. But the answer is there, deep changes. If you start with the sand there is no space for the big rock.
Let's take the problem in another way, with a lack of systemic oppression, would it still be a problem to have a concept of master/slave? Or just master in this case. It describes very accurately the technical concept. My ancestors were definitely salves to some Roman dude and in no way do I get hurt by the term.
Overall, I have no fundamental problem with using another name for the Git branch or describing my architecture another way, however it's like cleaning up your room instead of doing your homework: you're getting a sense of accomplishment for doing not so much.
And my fear is that a lot of the white people racing to ban "master" from their vocabulary are going to stop at this very effort because they feel they've done their part but this won't prevent them from shit-talking the Indian offshore team.
So yes, action often ends at acknowledgement and virtue signalling but this is the least bit that can be done to make work culture more inclusive. And uh, even if there are less people of colour (esp dark skinned folks) in tech doesnt mean they don't exist...