Have you ever thought about the words we use every day, especially in tech? It turns out, they can make a big difference! The Linux Foundation's Alliance for OpenUSD (AOUSD) and the Academy Software Foundation (ASWF) recently teamed up to release an Inclusive Language Guide.
This guide is all about helping create a more welcoming space in the world of 3D content and beyond.
Table of Contents
Why Inclusive Language Matters
It's simple: language shapes how we feel and interact. By choosing words carefully, we can build a diverse, fair, and welcoming culture in technology.
Some older terms, like 'master' and 'slave' in coding, might seem harmless to some, but they can actually make others feel quite uncomfortable.
Furthermore, idioms and jargon can confuse or exclude people. The guide helps us spot these tricky words and swap them for better ones.
What the Inclusive Language Guide Recommends
This helpful guide offers practical tips for developers and writers. It encourages everyone to think about their language choices. Here are some key ideas from the guide:
- Avoid words with a past: Don't use terms that might carry historical weight, especially concerning background, gender, age, or ability.
- Skip the jargon and idioms: Not everyone understands tech slang or sayings from one country. These can confuse or exclude people, and sometimes have negative origins.
- Show diversity in examples: When you write code examples or documentation, use varied names and situations.
- Ask if you're unsure: If a phrase feels off, just ask! Being mindful of our words helps a lot.
Common Words to Rethink
The guide also gives us common terms to reconsider, along with friendlier alternatives. Here are a few examples:
- Instead of 'master'/'slave', try 'primary'/'secondary'.
- For 'blacklist'/'whitelist', use 'deny list'/'allow list'.
- Swap 'man hours' for 'labour hours' or 'work hours'.
- Refer to a group as 'folks' or 'team' instead of 'guys'.
- Change 'sanity check' to 'validation check' or 'logic check'.
- When you hear 'grandfathered', consider 'established' or 'rollover'.
Real-World Efforts in Tech
Many companies in the tech world are already working hard on this. For example:
- Autodesk put together a special team to change insensitive terms across all their projects, rolling out changes in phases. They even created a shared document with terms and their standardised alternatives.
- DreamWorks Animation is also tackling this, especially with terms like 'master' in code branches. They are finding ways to make changes smoothly and encourage better language every day.
- Sony Pictures Imageworks is investigating which terms to change first, considering how easy the change is versus its impact. They also plan to explain clearly why these changes are important to their developers.
Read Inclusive Language Guide
The latest updated inclusive language guide can be found in the link below:
And, the previous guide is available in the following link:
Moving Forward, Together
Ultimately, making language more inclusive is a big team effort. It's about everyone working together to ensure that our words create a positive and respectful environment for all developers and content creators.
The AOUSD and ASWF's Inclusive Language Guide is a fantastic start, helping us build a future where everyone feels welcome in Tech and beyond.
