The Perception and Impact of Non-inclusive Language in Software Artifacts

📅 2026-07-01
📈 Citations: 0
Influential: 0
📄 PDF
🤖 AI Summary
This study addresses the lack of empirical evidence on how non-inclusive language in software artifacts affects developers’ sense of belonging, collaboration, and psychological well-being. Conducting the first large-scale online survey of 1,212 open-source contributors, the research systematically quantifies perceptual differences and psychological impacts associated with terms such as “whitelist/blacklist” across gender and geographic groups. Findings reveal that women and non-binary developers are significantly more likely to perceive these terms as exclusionary, which in turn correlates with markedly reduced feelings of belonging and overall well-being. By providing robust empirical support for the tangible harms of non-inclusive terminology, this work offers critical evidence to inform and motivate inclusive language practices within technical communities.
📝 Abstract
Terminology such as "whitelist/blacklist," "master/slave," "man-hours," or "dummy value" has long been part of the technical vocabulary used in software artifacts, including source code, version histories, and documentation. In recent years, however, many of these expressions have been recognized as potentially non-inclusive and unwelcoming to groups historically underrepresented in software development, such as people of color, women, and individuals with disabilities. Consequently, a growing movement within the software industry has sought to replace these terms with more inclusive alternatives. Despite these initiatives, little is empirically known about how software developers perceive such terminology or how its continued use may influence their professional experiences and sense of belonging. This paper addresses the knowledge gap by examining how software developers perceive non-inclusive terminology in software and its perceived impact on team dynamics, productivity, belonging, and well-being. We surveyed open-source contributors and received 1,517 responses, of which 1,212 were complete and analyzed. On average, respondents reported low negative workplace impact overall; however, perceptions and impacts varied by demographic group. Women and non-binary participants, as well as respondents residing in the United States, were more likely to view the terms as non-inclusive. Among those who considered the terminology non-inclusive, non-binary participants reported higher overall negative impacts than male respondents, and female participants reported higher impact specifically on their sense of belonging.
Problem

Research questions and friction points this paper is trying to address.

non-inclusive language
software artifacts
developer perception
sense of belonging
diversity in software development
Innovation

Methods, ideas, or system contributions that make the work stand out.

inclusive language
software terminology
developer perception
diversity in software engineering
empirical study
🔎 Similar Papers
No similar papers found.
A
Ahmad J. Tayeb
Department of Information Technology, Faculty of Computing and Information Technology, King Abdulaziz University, Jeddah, Saudi Arabia
M
Mohammad D. Alahmadi
Department of Software Engineering, College of Computer Science and Engineering, University of Jeddah, Jeddah, Saudi Arabia