I am pretty sure at 25, I can stand reading "He xxxx" in documentation.
The issue isn't the words, it is assuming no one besides someone like you should work on the project.
I am pretty sure at 25, I can stand reading "He xxxx" in documentation.
The issue isn't the words, it is assuming no one besides someone like you should work on the project.
These are the minute bricks of social construction, and we can either choose to ignore them (and replicate existing oppressive social structures) or fix them (and make conscious choices about the society we construct).
If, indeed, you are opposed to women programming, I can think of no better long-term solution than persistently emphasizing the maleness of technology or exclusively using male pronouns.
To come out and blankly state that "women should not be in programming" would be met with the Backfire Effect, so subtlety is necessary, here. Keep up the good work.
What's maybe more of an issue is that is there is a long-term bias in the use of gendered language, across multiple projects, in code and documentation and comments, then that does seem like an obvious bug. It's a very small thing, but one of those things that in aggregate could contribute to the perception of a more general gender imbalance in the industry.
But think off it another way – for no cost, you can make other people feel slightly more comfortable in the long term working in this field. Why bother fighting it?
Personally, I tend towards the second-person (you) or indeterminate third-person (they, one) if not referring to a specific person.