4 ms·
If the terminology is (1) non-descriptive (it is, especially in comparison to the various _alternatives_ that describe very different scenarios) and (2) offensi
by halostatue 6y ago
If the terminology is (1) non-descriptive (it is, especially in comparison to the various _alternatives_ that describe very different scenarios) and (2) offensive to people, why not change it?
But let‘s be clear: there’s a race problem in technology, just as there’s a gender problem in technology. If someone whose ancestors were enslaved were working in technology and encountered the terms master/slave … how would they feel? Would this be another of the thousands of microagressions that they face working in technology today? Would they ultimately leave technology because they can’t get any of their white coworkers to take these microaggressions seriously?
The answer, of course, is an ongoing yes to all of those. This is a trivial way to remove offensive microaggressions, and the pushback that is being received to this makes it very clear to racialized peoples that the real privilege is in the people who object to these inaccurate and offensive terms being changed for something more accurate and inoffensive.
- root_axis 6y agoThere is absolutely a race problem in technology starting with the pipeline problem, extending into discrimination, salary disparities, microaggressions etc and I don't believe microaggressions are trivial. I disagree that the use of the master/slave terminology in technology is racialized and I also disagree that it falls into the category of microaggression. A microaggression is e.g. "but you listen to rap right?" or "what exactly are you?" or "wassup homie" directed only at black people. If the comment or action is not directed at a person it's not a microaggression. Finally, I am not opposed to changing the terminology, I think alternative words are fine, I just think now is perhaps the worst possible time in hisory to litigate this issue.