Heard of suss? You can suss out more information or you can find someone's information to be suss. "Suss" shows the flexibility of language. It’s an ongoing process to change how we use certain words. It's important to choose words carefully to convey the correct meaning and avoid harmful subtext or exclusion. Let's explore some of the tools and triage methods it takes from an engineering viewpoint to make bias-free choices. How can you ensure that biased words do not sneak into code, UI, docs, configurations, or our everyday language? First, let's walk through how to take an inventory of assets from code to config files to API specifications to standards. Next, by placing those findings into categories, prioritize the work to substitute with inclusive alternatives. Let's examine some examples using both API and code assets. Next is a demonstration of how to automate analyzing your source code or documentation with a linter, looking for patterns based on rules that are fed into the tool. What's in the future for these efforts? Inclusive language should expand beyond English and North American efforts. To do so, let's organize the work with automation tooling, as engineers do.

1. Anne Gentle, Developer Experience Manager, Cisco
CodeMash
January 12, 2023
Bias-Free Language in Code and Configurations
Inclusive, Accessible Tech:

2. © 2023 Cisco and/or its affiliates. All rights reserved. 2
© 2023 Cisco and/or its affiliates. All rights reserved.
The presentation today will touch
on sensitive topics, including
language that may be harmful to
some audience members.
We will be sharing our efforts to
remove this language from our
products, content and culture at
Cisco.
If at any point you feel
uncomfortable, please feel free to
exit the session, and reach out
directly with questions, or requests
for more information in a format
that works for you.

3. © 2023 Cisco and/or its affiliates. All rights reserved. 3
Hi!
I’m Anne Gentle, a Developer Experience
Manager at Cisco.
We make Cisco APIs better for developers.
We treat docs like code for over 1000 code
repositories for multiple products and platforms
at Cisco.
I play tennis, kayak, hike, paddleboard, and
work in Austin, Texas.

4. © 2023 Cisco and/or its affiliates. All rights reserved. 4
© 2023 Cisco and/or its affiliates. All rights reserved.
Check out my book:
Docs Like Code
Third Edition

5. © 2023 Cisco and/or its affiliates. All rights reserved. 5
Social Justice Journey
Overview
Policy to Practice
Code and Config Examples
Resources and Questions

6. © 2023 Cisco and/or its affiliates. All rights reserved. 6
© 2023 Cisco and/or its affiliates. All rights reserved.
Power an Inclusive
Future for All
We must help bridge gaps of
inequity by using our technology,
extended ecosystem, and the
expertise of our teams, while
creating more opportunities
for more people, and acting
responsibly to drive change.
- Chuck Robbins

7. © 2023 Cisco and/or its affiliates. All rights reserved. 7
© 2023 Cisco and/or its affiliates. All rights reserved.
Cisco’s Social
Justice Actions
1. Influence Ecosystem
2. Increase Representation
3. Expand Pay Parity
4. Increase Board Diversity
5. Deliver Anti-Discrimination Legislation
6. Connect Leaders and Employees
7. Supplier Engagement
8. Commit to HBCUs
9. Support Black-Owned Companies
10. Diversify Partner Ecosystem
11. Invest in Innovation
12. Human Rights in Technology Solutions

8. Human Rights by Design
Advise & Train Product Teams on
Human Rights throughout the
Product Development Lifecycle
Accessibility by Design
Advise & Train Product Teams on
Accessibility throughout the Product
Development Lifecycle
Inclusive Naming
• Implement Cisco’s Inclusive Language Policy
• Build Employee Awareness about Inclusive Language
• Drive Compliance across Cisco’s Functions
• Engage Community and share Best Practices
• Embed a Culture of Belonging via Governance Models
Social Justice in Product Development

9. Inclusivity encompasses multiple aspects
• Gender neutrality including
pronouns, non-binary typing
• Respectful language without
drawing upon stereotypes
• People first, humans are humans
not abilities or diagnoses
• Inclusive representation and
avoiding idioms like "up in the air"
• Accessibility including screen
reader experiences

10. © 2023 Cisco and/or its affiliates. All rights reserved. 10
Policy to Practice

11. © 2023 Cisco and/or its affiliates. All rights reserved. 11
Policies on Inclusive Language
Goal: Promote and facilitate replacing harmful and exclusionary language in tech
Term
Recommended
Replacements
master / slave
primary/secondary
or
primary/subordinate
or
control/data (for clustering)
whitelist /
blacklist
permit (list)/block (list)
or
allow (list)/block (list)

12. © 2023 Cisco and/or its affiliates. All rights reserved. 12
© 2023 Cisco and/or its affiliates. All rights reserved.
Tier 2, Tier 3
Word Lists

13. © 2023 Cisco and/or its affiliates. All rights reserved. 13
© 2023 Cisco and/or its affiliates. All rights reserved.
No Change
Word List

14. © 2023 Cisco and/or its affiliates. All rights reserved. 14
© 2023 Cisco and/or its affiliates. All rights reserved.
Word Lists like an
API Contract
• Version-locked; users
know which version to
expect the change.
• Documents the dates to
expect the change.
• Backwards compatibility
means no breaking
changes due to a word
change.
• Communicates a roadmap
for future word changes.

15. © 2023 Cisco and/or its affiliates. All rights reserved. 15
Driving compliance requires that we know what
compliance means
input output
Internal Code
APIs, GUI, CLI, etc. Logfiles, telemetry,
etc.
Product
documentation
Automated checks in CI/CD

16. © 2023 Cisco and/or its affiliates. All rights reserved. 16
Our goal is to build and foster community for best practices
and iteration with:
People
Key Stakeholders with a
disproportionate amount of
influence:
• Platform leads
• Tech program managers
Roles impacted:
Product Managers and
Engineering Leaders who
are struggling to keep up
with their backlog
Communities:
Internal & External
community to share best
practices
Process
Sequence:
1. Inventory Report
2. Create Change Plan
* What will you change and
by when?
* What won’t you change and
why?
* What is still TBD and why?
3. Tracking &
Communication
Tools
Tools, Code, and Programs
to enable engineering
compliance:
InclusiveNaming.org
Content sharing via Internal
Github repository &
SharePoint
Inventory Helper Tool
Automated mitigation via
open source: “get woke”
inclusive linter rule checker
Engineering playbook
Monthly Best Practice calls

17. © 2023 Cisco and/or its affiliates. All rights reserved. 17
Code and Config Examples

18. Category #1
Variable names
or comments that
are internal to
code. No impact
to customers and
no external
visibility.
Asset Categories
Category #2
CLI (config, show),
API, or schema
use. Deprecate
the old use and
create a new one
with a text alias.
This is complex
and customer-
facing; new and
old must work.
Category #3
Logs, telemetry,
monitoring:
Support old and
new (don’t break
customer scripts).
Deprecate the old
but cutover to
new.
Category #4
Documentation
changes: Simple
cases are easy to
do. Complex cases
(like documenting
a CLI) must follow
product changes.
Code and Configuration Examples

19. © 2023 Cisco and/or its affiliates. All rights reserved.
© 2023 Cisco and/or its affiliates. All rights reserved.
https://github.com/CiscoDevNet search for “slave”
Category 1 example

20. © 2023 Cisco and/or its affiliates. All rights reserved.
© 2018 Cisco and/or its affiliates. All rights reserved.
Inventory tool:
github.com/cisco-open/
inclusive-language
Requires a GitHub
personal access token.
Refer to the GitHub
docs for creating a
personal access token.
Scope the token for
read-only access.
Scripts
gh_search.py
Creates an inventory of which files contain keywords that you no
longer want to use, creating a comma-separated listing that you
can use for further analysis.
gh_default_branch.py
Looks for repos that have the default branch set
to master instead of main. You could modify that script to create
an Issue automatically in any repo that meets that criteria, or
simply run the script as a report for analysis.

21. © 2023 Cisco and/or its affiliates. All rights reserved. 21

22. © 2023 Cisco and/or its affiliates. All rights reserved.
© 2023 Cisco and/or its affiliates. All rights reserved.
https://github.com/cisco-open/inclusive-language

23. © 2023 Cisco and/or its affiliates. All rights reserved.
© 2023 Cisco and/or its affiliates. All rights reserved.
Thanks to Python and GitHub! An Excel inventory

24. © 2023 Cisco and/or its affiliates. All rights reserved.
© 2023 Cisco and/or its affiliates. All rights reserved.
API Example:
API field name
changes
Firepower Management Center
REST API v7.1
Field Names (returned JSON)
Category 2 example

25. © 2023 Cisco and/or its affiliates. All rights reserved.
Example:
DevNet Associate
Fundamentals Course
Category 4 example

26. © 2023 Cisco and/or its affiliates. All rights reserved.
Mitigation Example:
Ruleset for “woke”
linter and
Jenkins job

27. © 2023 Cisco and/or its affiliates. All rights reserved.
Visual Studio Code:
AlexJS Linter
Extension

28. © 2023 Cisco and/or its affiliates. All rights reserved.
© 2023 Cisco and/or its affiliates. All rights reserved.
How can I check my
code and user-facing
documentation against
our policy?
How do we know if our
code base is compliant?
Scanning & Reporting
Scenarios for Tools
What data can tell us
when it’s critical to add a
term to our policy?
How do we quantify our
risk exposure based on
the current policy?
How do we measure the
amount of change
needed for today’s
policy?
How do we measure the
impact of a change in
our policy?

29. © 2023 Cisco and/or its affiliates. All rights reserved. 29
Looking Forward:
New Terms and Impact on Code vs. Culture
Goal: Centralized governance for policy and language decisions
Begin New
term
Culture
or Code?
Engineering Change
Process
General
tool/documentation
update
End
Questions that keep us up at night:
1. Governance structure – Which terms are critical enough to justify a company-wide
change in code, and why? And How?
2. US vs. Global intake process – Why wouldn’t we include global terms in our policy?
3. Scale - How do we meet all language needs for all roles?

30. © 2023 Cisco and/or its affiliates. All rights reserved. 30
Resources and Questions

31. © 2023 Cisco and/or its affiliates. All rights reserved. 31
Inclusive Language Resources
Inclusive Naming Initiative
Language recommendation lists
https://inclusivenaming.org/word-lists/
Example Public Policy on Inclusive Naming
https://www.cisco.com/c/en/us/about/
social-justice/inclusive-language-policy.html
Inventory Tools and Example Ruleset
https://github.com/cisco-open/
inclusive-language

32. © 2023 Cisco and/or its affiliates. All rights reserved. 32
What can you do to advance Inclusive Language?
Take an inventory of your engineering assets (code,
log files, telemetry data, standards).
Take a moment to reflect on your own use of language.
Consider what you can do in your role, and with your
unique skills, to advance this work.
Take a Linux Foundation training on inclusive speaking
(LFC101) and inclusive open source practices (LFC102)

33. © 2023 Cisco and/or its affiliates. All rights reserved. 33
Thank you!
Inclusive, Accessible Tech:
Bias-Free Language in
Code and Configurations
Anne Gentle
Developer Experience, Cisco
Twitter: @annegentle
LinkedIn: linkedin.com/in/annegentle
https://github.com/cisco-open/inclusive-language