Our playbook for driving down non-inclusive terminology
Overview
The article discusses Airbnb's initiatives to build an inclusive codebase by eliminating non-inclusive terminology within their engineering culture. It highlights the collaborative efforts of employees to identify problematic terms and implement a linter to promote inclusive language in code.
What You'll Learn
1
How to identify and eliminate non-inclusive terminology in a codebase
2
Why inclusive language is important for engineering culture
3
How to implement a linter to flag non-inclusive terms in code
Key Questions Answered
What steps did Airbnb take to address non-inclusive terminology in their codebase?
Airbnb organized a volunteer effort to identify non-inclusive terms in their technical stack, co-authored a proposal for change, and implemented a linter to flag these terms in pull requests. This initiative was supported by management and involved collaboration with affected communities.
How does Airbnb ensure that engineers understand the reasoning behind changes to terminology?
Airbnb documents the reasoning and history for each non-inclusive term in the linter comments, providing context and clarity to engineers. This approach helps them understand the importance of the changes and encourages compliance.
What role do Employee Resource Groups (ERGs) play in Airbnb's initiative?
Employee Resource Groups at Airbnb, such as Black@ and Able@, contributed to sourcing offensive word lists and implementing improvements. These groups provide a platform for employees to unite around shared characteristics and experiences, enhancing the inclusivity of the initiative.
How does Airbnb plan to evolve its list of non-inclusive terms over time?
Airbnb views the initiative as a long-term project, establishing a transparent process for updating the list of non-inclusive terms. This process involves diverse representation from impacted communities and considers the terms' impact on individuals and alignment with company values.
Technologies & Tools
Tool
Linter
Used to flag non-inclusive terms in pull requests and suggest alternatives.
Key Actionable Insights
1Implement a linter to flag non-inclusive terminology in your codebase to promote inclusivity.By integrating a linter, you can proactively prevent the introduction of non-inclusive terms, fostering a more welcoming environment for all developers.
2Engage with Employee Resource Groups to gather insights on inclusive language.Collaborating with ERGs can provide valuable perspectives and help identify terms that may be problematic, ensuring that your initiatives are well-informed and effective.
3Create an anonymous feedback mechanism for engineers to voice concerns about terminology.This approach encourages open communication and allows for continuous improvement in the inclusivity of your codebase, making engineers feel heard and valued.
Common Pitfalls
1
Failing to engage with diverse voices when identifying non-inclusive terms can lead to oversights.
Without input from affected communities, initiatives may miss critical terms that perpetuate exclusion, undermining the goal of inclusivity.
Related Concepts
Inclusive Language In Software Development
Employee Resource Groups And Their Impact
Long-term Strategies For Cultural Change In Tech