It’s definitely a fraught topic, but if you go in using loaded language like “fetishism” to describe a position that many people have rationally arrived at in good faith, then yeah people are going to call you a jerk.
Part of the reason that I don’t think your paragraph 1 assumption is flawed is that there is evidence that men and women were equally interested in programming before the 80’s, but that a combination of cultural and societal factors came into play in that decade that branded computers as a “boy thing” and resulted in women being pressured out of the pipeline from a young age.
But even if you can find some sort of counterargument for that, my overriding reason why I stick with this assumption is as follows: decade after decade, people insisted that women weren’t into $career. And one by one, women have found their way into those careers (factory work in WWII, the executive suite more recently, plenty of other examples in between). In each case, the people saying women weren’t into $career had an argument that seemed to make sense, often relying on some combination of status quo statistics and hand-wavy conclusions drawn from psychology. And they were wrong. So when I see those same arguments brought out again for this career (often with some exhortation that “this time is different”) I generally dismiss them, as the epistemology they’re based on has a bad track record.
With all that being said, when it comes to actions, I’ll be more likely to encourage women to get into programming if I get a sense they might be interested in it. However, when it comes to interviewing candidates, I will not grade people on a curve based on their identity, as it is my belief that men and women can in fact be equally good at programming and should be held to the same standard.
You're correct about my language choice, I could (and should) have used more neutral language to describe my position. While I do believe that there are some fundamental differences in the interests and abilities of the genders (neither for better nor worse, they just are) I also agree that's its a slippery slope that has been abused in the past. Societal pressures and conditioning certainly play a role, however I think if you look at the lower-end of the job market the difference is clearer. Women tend to dominate retail work as well as waitress/hostess positions while men tend to dominate more labor intensive positions like construction, welding, modern day factory work etc. Is this due to some rampant discrimination in those fields or is it due to inherit biological/psychological differences in men and women? I'd be inclined to say the later. There are no pushes happening in the bottom end of the job market due lessen the gender disparity because those aren't as desirable positions so no one really cares that more men work in construction and more women are servers at restaurants. However when the position becomes more prestigious with higher pay it's suddenly a huge issue that a disparity exists - and obviously it's due to discrimination and has nothing to due with what each gender is naturally inclined to pursue or enjoy.
You're right in that it's important not to automatically ascribe any demographic disparity to fundamental differences between the genders, but it's equally important to not automatically ascribe that difference to discrimination without considering those fundamental differences.
I disagree about the “equally important” stuff, and here’s why: If I’m wrong and the overwhelming majority of women really don’t like programming, I’ll have wasted some of my time, but no one will have been materially harmed[0]. However, if I am right, then there are currently a large number of people who are being pushed away from a career or hobby that could increase their overall happiness and/or standard of living if they were not being pushed out of it, and I see that as a potential tragedy.
Given how slanted these stakes are and how many times society as a whole has underestimated women as a whole, I think the right answer here is to err on the side of trying to get women and other underrepresented minorities interested into tech.
[0] bear in mind what I said about the particular way I’m putting my belief into practice and that I do not believe in “reverse discrimination” to even the scales.
That's fair. I do believe that in an ideal world, everyone's barrier to entry into any profession would be equal removing all factors except merit. While that's obviously not possible, I do think it's worthwhile to work towards that. I also think that it can be worthwhile to make it known to women that tech and other career paths are viable and not out of reach for them - as I'm sure some women just have never considered it just as I have never seriously considered becoming a nurse. However, I think that's where it should stop. Make it known that it's an option, make it so that if they choose to pursue it that it's no more difficult for them than it would be if they were a man, and then let it be.
Anything more and it becomes the individual(s) behind the movement projecting their desires onto others and is no different that the societal molding that's taken place for the past several decades.
The unstated major premise here is that software engineering work is valuable/fulfilling/high-status, while other work is not---so that pushing someone naturally suited to software engineering away causes harm, while pushing people more naturally suited to a different field into software engineering causes less harm.
I don't think your premise is wrong, but I think it does explain why computer science is particularly focused on broadening participation, compared to other disciplines like nursing, teaching, etc. Computer science is current (for better or ill) a golden ticket to economic mobility.
> there is evidence that men and women were equally interested in programming before the 80’s, but that a combination of cultural and societal factors came into play in that decade that branded computers as a "boy thing" and resulted in women being pressured out of the pipeline from a young age.
The nature of "programming" as an activity also changed quite a bit.
Part of the reason that I don’t think your paragraph 1 assumption is flawed is that there is evidence that men and women were equally interested in programming before the 80’s, but that a combination of cultural and societal factors came into play in that decade that branded computers as a “boy thing” and resulted in women being pressured out of the pipeline from a young age.
But even if you can find some sort of counterargument for that, my overriding reason why I stick with this assumption is as follows: decade after decade, people insisted that women weren’t into $career. And one by one, women have found their way into those careers (factory work in WWII, the executive suite more recently, plenty of other examples in between). In each case, the people saying women weren’t into $career had an argument that seemed to make sense, often relying on some combination of status quo statistics and hand-wavy conclusions drawn from psychology. And they were wrong. So when I see those same arguments brought out again for this career (often with some exhortation that “this time is different”) I generally dismiss them, as the epistemology they’re based on has a bad track record.
With all that being said, when it comes to actions, I’ll be more likely to encourage women to get into programming if I get a sense they might be interested in it. However, when it comes to interviewing candidates, I will not grade people on a curve based on their identity, as it is my belief that men and women can in fact be equally good at programming and should be held to the same standard.