No More ‘sanity Checks.’ Inclusive Language Guide Bans Problematic Tech Terms

A Linux Foundation project has published an Inclusive Language Guide to recommend replacements for common tech terms deemed potentially offensive to some users.

The updated guidelines, the initial version of which first turned up at the Academy Software Foundation in 2021, have been extended to include phrases used by engineers.

“Sanity Check,” for example, is out. Better to say something like “validation check” or “consistency check.” “Hung” is deemed to be a bit violent, and so the list recommends “stalled” or “unresponsive” instead.

The latter is a tricky one. We’d understand “Hanged”, since that refers to death by hanging, while “hung” is all about pictures. Then again, when an engineer says an app has “hung,” they’re rarely referring to popping it on the wall for all to admire. Perhaps they mean that it’s just hanging out and doing nothing.

We asked the Academy Software Foundation for clarification and will update this piece should the organization respond.

“Dummy” is also in the list of words that are recommended for swapping. “Placeholder” or “Stub” is included in the list of recommendations. And “pow-wow,” borrowed from native American culture? If you’re using that, then perhaps “meeting” or “huddle” might be better alternatives.

Other guidelines include recommendations around gender assumptions and the use of color to reflect a positive or negative characteristic. For example, you are asked not to use the terms “blacklist” and “whitelist.” Referring to a go-between as a “middleman” is out also.

The Academy Software Foundation (ASWF) and the Alliance for OpenUSD (AOUSD) are not the only organizations to update their Inclusive Language Guide. Google has its own Inclusive Documentation guidelines, which also wants you to avoid using the word “hang.”

The issue of inclusive language has rumbled along for a while now. Rolling it out in projects can present challenges; afterall, every person in a group should follow the same guidelines. As the ASWF notes, “Implementing change across whole repositories may require a unified team or studio effort.” It does, however, seem a worthwhile effort – what might not seem offensive to some could make others uncomfortable.

While the updated guidelines include new words and phrases to avoid and new recommendations for alternatives, the general advice remains the same: “If you’re unsure, ask!”

Wise words. The updated guidelines no doubt contain some elements that generate an eyeroll or two, but if looking at some text, asking the question, and perhaps saying things differently can save a coworker unnecessary discomfort, then why not? ®

Original Source