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.
> 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.