For example, for many years Law was 95% male. You could say that it was a masculine profession because it’s all about conflict while women prefer peacemaking. But today 50% of new large firm attorneys are women. Law isn’t any softer or gentler now—in fact it’s probably less civil. Same for teaching. We explain teaching being dominated by women on the basis that teaching is about nurturing. But in India, the vast majority of teachers are men.
You could easily say that programming is feminine. It’s not at all physical, all about cooperating and communicating with other people, it’s about managing expectations, etc.
Also, the truck analogy has been debunked. It’s explained by the fact that girls have a higher affinity for faces than boys. Which makes sense: infants don’t have any association between trucks and masculine professions like construction work. They can’t. Any gender difference observable at a very young age has to be unrelated to the associations adults have between trucks and masculinity.
I would characterize programming as very far on the “Things” side of the axis that is “People vs Things”.
See: Men and Things, Women and People: A Meta-Analysis of Sex Differences in Interests
https://pdfs.semanticscholar.org/47af/4a7e87267aba681fb69715...
The fundamental task of programming – sitting in front of a computer, reasoning about the machine and the system, and writing code and debugging systems for hours on end — is about as “thing”-oriented as I can conceive of. One needs to do a great deal of this to get a CS degree.
Another dimension to consider is Systematizing versus Empathizing (citations omitted). Programming seems to be far on the systematizing side.
As a thought experiment, what jobs might be further on the side of “things“ and “systematizing” than programming?
(I don’t know of any studies that characterize the programming in these dimensions. I’m providing my intuition.)
I’m not super familiar with the practice of law, but I would guess that it’s actually fairly close to the middle of both of those spectrums. The law itself is systematic but practicing it involves working with people at every level (client, counterparty, judge, regulator). It’s possible to write and deliver code, or root-cause and fix a bug report, without interacting with another soul.
> why we have any reason to believe that programming is a “masculine” profession
By exclusion: we have checked everything else we could think of and found no other logical explanation for the disparity of sexes in STEM. That doesn't mean women's preference is the true underlying reason, but then, we don't have a better explanation, or even any other explanation consistent with facts. Still, AFAIK, Damore never claimed it was THE reason, he just raised it as a possible and the likeliest explanation - given no other explanation seems to work.
> But in India, the vast majority of teachers are men.
I don't think India is a valid example here, because there is still a lot of inequality in that society. Let's talk about countries on the higher end of the equality spectrum, like Finland or Sweden.
> Also, the truck analogy has been debunked
[Source missing]
> The fundamental task of programming – sitting in front of a computer, reasoning about the machine and the system, and writing code and debugging systems for hours on end — is about as “thing”-oriented as I can conceive of. One needs to do a great deal of this to get a CS degree.
From the GP:
>You could easily say that programming is feminine. It’s not at all physical, all about cooperating and communicating with other people, it’s about managing expectations, etc.
Here's the real disconnect, and it's all about the environment that is cultivated wherever you happen to be. These are really two wildly different professions that happen to be lumped under one title. On the one hand you have the concrete, generative work where you are creating a thing out of the void. And on the other, you have the political infighting and jockeying to be allowed to do that generative work, and all of the overhead involved in such operations. These are wildly disconnected activities, and it should be no surprise that people gravitate towards one extreme or the other, with very few rare unicorns that can do both at a high level.
The practice of law at a business firm (where 50% of associates are women) occasionally involves people, but for the most part is thing oriented. I do less coordinating with team members and the client than when I was an engineer, because everything is on the record. You don’t have long meetings with the client to get their use cases, etc. When you do interact with people it’s systematized and highly artificial. Youre not trying to connect with the judge as a person. You’re breaking down an often highly abstract issue into constituent parts to help the judge understand it. And the things you’re dealing with are typically more abstract. The subject matter isn’t a website with pictures or human users. The subject matter is a lien, or a credit default swap, or a regulation embodying an economic theory. You talk about these abstractions as if they were things.