Software evolves, and so does culture.
TL;DR: Avoid old terms like whitelists, blacklists, master, etc.
- Use alternative terminology
Language evolves, and technical terms should follow it.
You can change racial names with alternative terminology:
Allowlist: Replace "whitelist" with "allowlist." This term maintains the intended meaning without racial connotations.
Denylist: Substitute "blacklist" with "denylist." This term conveys the same concept without perpetuating negative racial associations.
Permit List and Block List: Another option is to use "permit list" in place of "whitelist" and "block list" instead of "blacklist."
Main branches: You can replace "master" with "main".
Master/Slave: You can replace them with Primary/Replica/Mirror etc.
val whitelist = listOf("Barbie", "Ken") val blacklist = listOf("Midge") val gitCommand = "git pull origin master" val process = Runtime.getRuntime().exec(gitCommand)
val allowlist = listOf("Barbie", "Ken") val denylist = listOf("Midge") val gitCommand = "git pull origin main" val process = Runtime.getRuntime().exec(gitCommand)
You can set up a denylist (not a blacklist) of terms you need to double-check for accuracy.
- References to old manuals
Just as we refactor code to enhance its quality, we should also refactor our language and terminology to promote inclusivity and diversity.
By eliminating racially insensitive terms like "whitelist" and "blacklist" in favor of more inclusive alternatives, we contribute to a more equitable and welcoming tech industry.
Let's embrace change and create a coding environment where everyone feels valued, regardless of their background or ethnicity.
Code Smells are my opinion.
An ultimate joint challenge for the biological and the computational sciences is the understanding of the mechanisms of the human brain, and its relationship with the human mind.
This article is part of the CodeSmell Series.