Inclusive Programming Language
In recent months many Open Source projects and various different companies have encouraged their software engineers to use inclusive terminology in code and documentation. Here’s a short list:
Inclusive Coding Terms
Proposed alternatives for master/slave:
- primary/secondary
- leader/follower
- main/replica
- initiator/target
- requester/responder
- controller/device
- host/worker
- director/performer
Proposed alternatives for blacklist/whitelist:
- denylist/allowlist
- blocklist/passlist
- redlist/greenlist
- stoplist/golist
Proposed alternatives for man hours/days:
- person hours/days
- engineer hours/days
- dev hours/days
Proposed alternatives for gendered pronouns (he/she, his/her):
- Use plural (they, their) if possible
Proposed alternatives for sanity check:
- quick check
- confidence check
- coherence check
Proposed alternatives for dummy value/data:
- placeholder
- sample
- example
Proposed alternative for indentation with spaces:
- Indent with tabs (SCNR ;)