3 ms·
My reaction was "If you want to write some documentation with bias-free language, just write the documentation with bias-free language." Why the need for a long
by hn_throwaway_99 4y ago
My reaction was "If you want to write some documentation with bias-free language, just write the documentation with bias-free language." Why the need for a long paragraph explaining "Look how great and sensitive we are!"
I understand, and agree with, the desire to use inclusive language, but so much of this has just devolved into performative nonsense.
Edit: Thought I'd leave my original statement above up, but after reading some of the other comments below I at least understand now the purpose of this notice. Basically, when it comes to Cisco's products, they previously used "master/slave" and "whitelist/blacklist" in their terminology, but no longer do. However, of course some older networking products still use that terminology in UI software, for example. So this notice is essentially saying "We got the memo about updated language, but if you see the terms master/slave or whitelist/blacklist in our docs, it's because it's essentially referencing something out of our control to fix, so don't yell at us."
- mlyle 4y agoElse you get questions, like, "why don't you say master/slave like everyone else?!@!!"
- kwhitefoot 4y agoAt this stage I think such questions can just be ignored.
- MarcoZavala 4y ago
- alpb 4y agoSaying that and usernames like "DoneWithAllThat" and "hn_throwaway", yeah, it checks out.
- hn_throwaway_99 4y agoNot sure exactly what point you're trying to make, but if it's "the risk of saying anything even remotely critical of DEI tactics is a huge, gargantuan, giant career risk these days", then I wholeheartedly agree.