Yeah, but people-based metrics are subjective, even if they have hard numbers stuck in there. That's the problem.
The mistake here is viewing the entire system as simple, instead of emergent. Emergent systems are not usefully measured by simplistic top-down metrics.
You have one piece of code, yep, you set up some measurements and have fun with it. You have a thousand programs, running across a hundred different platforms? The idea that you can determine cause and effect by a simple top-down metric is a problem in itself. Yes, you may be able to determine that overall the system is not working as you would like it to be, and you may certainly decide that some kind of action is required, but that gives you no clue whatsoever what the required changes would be! In fact, by looking from the top-down in an aggregate fashion, it's even arguable whether or not your metric is the one to be optimized!
That's the difference between complex systems and simple systems. Stop over-simplifying. We all might be able to agree that some aggregate statistic is out of whack. Maybe. But that's a freaking long way from actually knowing anything about the problem or what to start doing to address it. Instead, we wrap it all up like that answer is straightforward, wave our arms around, get all emotional, and demand action. This is not a recipe for success, whether in complex systems of programs or complex systems of people.
I can't express how infuriating I find the "we just need to treat everyone equally, that's it!" type of comments, and these analogies help me understand why. It's like saying "we just need to write maintainable modular code, that's it!"
I am more infuriated by the idea that if women are underrepresented in technical fields, it must be the fault of the men in those technical fields. After all, if men would just treat women equally, then women would represent half the workforce in those fields, right?
Women are underrepresented in applications to engineering school. Are adults who are already in the workforce responsible for that? Do high school girls somehow sense the "hostile environment" in engineering schools before they spend a single day there? If we want to actually solve this problem, we need to go all the way to the beginning: middle school, where girls mysteriously start losing interest in technical fields.
> Do high school girls somehow sense the "hostile environment" in engineering schools before they spend a single day there?
My wife, who has a solid head for mathematics but majored in German once explained to me why she didn't go into engineering: 1) because she didn't want to be surrounded by dudes all day; 2) because she didn't want to enter a field where she wouldn't have women bosses and mentors.
So if you're a high-school girl doing even a minimal bit of career planning, yes, of course you take into account the fact hat you'll be a minority in your field if you go into engineering, with all of the career hurdles that being a minority in any field entails.
> My wife, who has a solid head for mathematics but majored in German once explained to me why she didn't go into engineering: 1) because she didn't want to be surrounded by dudes all day; 2) because she didn't want to enter a field where she wouldn't have women bosses and mentors.
Then her own prejudice is keeping her out of engineering. That’s not the fault of the men in that field, that's all on her.
Also, you say she has a "solid head for mathematics" but instead majored in German. Again, that was her choice and this may be why many women don't go into technical fields: they simply choose not to (regardless of their abilities).
Perhaps so, but there is nothing people working in the field can do about that. If women are a minority because they are unwilling to join a field where they are a minority, then nothing that men do to change their behavior, attitude, or whatever else will solve the problem.
I also have some doubts about this being the sole issue. As an undergrad, I watched my school work hard to try to play up the fact that there were female students, female professors, and famous women in engineering. This was done whenever potential students were visiting. This was done in pamphlets sent out to high schools. The effect was not even measurable. I see the same pattern in my graduate program, and the same pattern in other engineering schools, and even among recruiters for corporations. I am not sure what else people in the field can do to try to dispel the notion; if indeed this is a cause, I suspect that girls are learning to dislike engineering from somewhere else, but I think that something happens earlier in life, at least if we believe the research on when girls lose interest in technical fields (somewhere around middle school or early high school).
There absolutely are things STEM workers can do. If it's a cultural problem in STEM, then we can work to change our culture. If it's a cultural problem with the perception of STEM, we can work to change the perception of STEM.
1. If it's us, then honest self-examination can reveal what we're doing wrong. Are we patronizing towards the women we work with or who are in the ranks below us (grade-wise in school, hierarchically in the workplace) more than we are with the men? Are they more sensitive to it, if so can we change how we approach them to be less off-putting?
2. If it's the wider culture in the US, we can participate in programs that reveal the reality of STEM to a broader audience. Help with youth mentorship programs. Become a teacher. There are many good math and science teachers, but there are many terrible ones too. I like my friends, but some of them teach math because that's what they were qualified to teach by credit hours, not because of an innate interest or understanding. They don't convey the sense of interest and itrigue that can capture children's attention and interest.
3. The reality is some combination of the above, our institutions (educational and professional) contain a great deal of systemic, often unintended, bias. Our media portrays engineers as lonely losers or creeps. As a community we can work to tackle these things if we take it on as a real challenge, instead of dismissing it as just gender differences.
> Perhaps so, but there is nothing people working in the field can do about that. If women are a minority because they are unwilling to join a field where they are a minority, then nothing that men do to change their behavior, attitude, or whatever else will solve the problem.
Sure they can. They can simply hire more women. Once the gender ratio is sorted out, the new equilibrium will be self-sustaining.
You're smart enough to know it's not that simple; even if one were willing to "just do it" it's not clear the unintended consequences would not result in a net-negative effect on women in engineering.
Fundamentally, if the source funnel is unbalanced, and you assume that there is a scalar "skill" quantity that is the economic factor of production employers actually desire, then it is mathematically impossible to hire-toward-parity without having a lower standard for hiring from the less-represented pool [0].
If you accept that ratio-correcting hiring mathematically necessitates lower standards for women then you need to answer some thorny economic questions.
Will the women whose skill is below the minimum skill of the men in your quota system be paid the same as the men (all of whom by mathematical necessity, will be more skilled)?. If they are paid the same as the men, it is a subsidy paid by the employer, the employer's customers, and the disemployed men who otherwise would have been hired but-for the quota. It's not clear to me that they bear any culpability for the social problem, or that the economic costs of this subsidy are sufficiently small not to have significant negative effects on those businesses. I know, I know: boo hoo, those poor businesses won't have two golden swimming pools of money, just one. But the reality is that the margins most businesses have between the cost of employment and the productivity of that employment is not, for most companies, rich Google-y numbers like 50%. If the margins are more like 10% it is entirely credible to me that such a subsidy will drive various arms of the business from ROI-positive to ROI-negative (or at least, ROI below just investing that cash in stocks). And then all those jobs we were planning to give to women will no longer exist.
If, on the other hand, the lower-skill women are paid sufficiently less than the men to balance the opportunity cost borne by the employer (for not being able to hire everyone above a minimum skill level) then the women need to be paid less than an open market wage (i.e. less than their skills would justify without a quota system, because the quota system is costing the employer lost productivity in men they would otherwise hire). So now the women are paying for the parity-seeking hiring. This will exacerbate the already high level of concern about fairness in compensation and will provide an additional disincentive for women to join this work force. Never mind that it seems perverse to have the women pay the employers for the privilege of working in a quota system.
Let me make a defensive statement lest it seem I am suggesting that women are less skilled than men: I am emphatically not. I'm saying that if you take the best five of 30 people and the best five of 100 people, the latter group will, with significant statistical regularity, be more skilled.
So what to do if ratio-correcting hire is DOA? It seems that there's an easier solution that has its roots in a long history of women conquering other obstacles; a generation of high-school aged women need to decide, en masse, that they will join engineering departments as a group and that they will stick to it with mutual support. This is direct action by the people whose well-being we are trying to improve, can be done without getting permission or cooperation from anyone outside that group, and solves the "boys' club" problem on day 1 of freshman year classes (because the club will be, by construction, full of women as well). I even have a slogan ready for them: "We're here, we're engineers, get used to it." I realize that coordinating this kind of movement is hard, but it is run-of-the-mill political and social organizing, and it seems to me like something that can actually work (as opposed to solutions that attack the symptoms of a skewed sourcing funnel).
[0] Proof sketch (hand-waving law-of-large numbers arguments, and assuming women's skills are distributed identically to men's):
1) If you reject quotas and hire simply for skill >= min_skill, then you will find more men meeting that criterion because there are men in the source funnel. So fixed-skill cutoffs are out.
2) If you have quotas (say 1 woman for every 1 man) then you can't hire everyone >= min_skill; you will instead hire the best among the people >= min_skill. The men will be pulled from a larger pool, and taking the best from a larger pool will result on average in a higher minimum skill level. So simply by taking the best N of the women and the best N of the men, the source funnel imbalance forces you to have lower standards for women
> I am more infuriated by the idea that if women are underrepresented in technical fields, it must be the fault of the men in those technical fields.
Who's saying that?
> If we want to actually solve this problem, we need to go all the way to the beginning: middle school, where girls mysteriously start losing interest in technical fields.
What do you mean by "go to middle school" - who do you suggest should take what action in that particular venue?
> mysteriously
What's mysterious about it? What expectations do you have that this observation runs counter to? What needs to be changed in our mental model of this system, so that instead of this being a mystery it becomes a predictable of the system's properties? (At which point we can start asking "how to change the system so that we get different outcomes".)
I'm only replying to the second question. In the US at least, it seems (and at one point I might have been able to point to the studies) that interest in STEM drops off[1] for female students around middle school, same for minority students. Many efforts at outreach, then, have tried to focus on introducing extracurricular academic programs at those students (often by targetting schools with higher female or minority populations) in an effort to cultivate their interest and maintain it through high school, in the hopes that it can increase the number participating in STEM in college and, later, the workforce.
At this point, however, I don't know what measurable impact those programs have had, I should probably talk to the folks I know that are still participating in the programs at a level where they monitor the trends.
Regarding who: Anyone working in STEM with the patience to deal with 12 year olds. Volunteer with FIRST Robotics teams or other after school or summer programs. Female and minority volunteers, in particular, as knowing that there are female and minority STEM workers isn't the same as knowing female and minority STEM workers, it can make a huge difference for kids.
[1] EDIT: It may not be a drop off. It's been too long since I was involved with this, but perhaps instead of them losing interest it's that they don't develop the interest at this point?
Show, don't tell. Provide an opportunity, guide them through solving interesting problems, set up the problems in ways that can appeal to them: competitions like FIRST Robotics; real world connections like rudimentary or introductory mechanical and electrical engineering and how it can solve their problems.
I can tell my functional programming hating program lead all day that it's great and very applicable to what we do, or I can write up a program we've been needing for months in two days and 200 clear lines versus the 2000 line C# version that's still got bugs in it.
"> I am more infuriated by the idea that if women are underrepresented in technical fields, it must be the fault of the men in those technical fields.
Who's saying that?"
Well, the article itself:
Promoting equality in your organization
If you start actively working to attack inequality in your organization, I guarantee you’ll realize you were already a feminist.
When your heart’s in the right place and you’re constantly examining your own actions and your organization’s, you start to notice bias and prejudice in more and more places. Most disturbingly, you notice it in yourself.
The implication in all of this is that there is inequality in our field that is due to our behavior i.e. the behavior of adults in the workforce. It is simply assumed that if we promote equality in our profession, and make it a team effort, then we will get equality.
"What do you mean by "go to middle school" - who do you suggest should take what action in that particular venue?"
I did not claim to have a solution, I was just pointing out where the problem lies. At some point in a girl's life, long before she is even thinking about college, something happens to undermine her interest in science and math. Years down the road, she winds up majoring in something that is not engineering or computer science, and fails to acquire the technical skills needed for a career in such fields by any other means. Obviously this is not something that all girls experience, but to a large extent it is the reason that engineering schools have so few women and so many men.
Maybe it is something girls are seeing on TV. Maybe it is something they are reading on the Internet. It is pretty clear that a young teenager is not seeing whatever prejudice exists in the workplace (how often do middle schoolers wander into your office?).
"What's mysterious about it? What expectations do you have that this observation runs counter to?"
Absent some reason to think otherwise, why would anyone assume that girls who have a talent and interest in math before a certain age would suddenly abandon their interest upon reaching that age? If puberty is the answer, why does it not happen to boys? For that matter, why does it seem to happen to a different degree in our country than in others?
> The implication in all of this is that there is inequality in our field that is due to our behavior i.e. the behavior of adults in the workforce. It is simply assumed that if we promote equality in our profession, and make it a team effort, then we will get equality.
I feel like you're getting something else out of this article than I did. The previous section, heading: Wanting equality isn’t enough, seems entirely contrary to the conclusion that you're drawn. The author is indicating that promoting/wanting isn't enough. We have to develop an understanding of why the situation is what it is, and actively work on shifting our culture to rectify it (assuming you think it's a problem in the first place, many around me don't).
Social pressures both to differentiate and conform to a particular sub-group during adolescence, and the kinds of groups that girls and boys tend to form. At least in part.
The OP might mean it in a more general sense in that we all have our biases, men and women included. It's just that men's biases might be more problematic in this case, since they're the majority in this field so any common bias they may have gets compounded.
> Do high school girls somehow sense the "hostile environment" in engineering schools before they spend a single day there?
Quite possibly, potentially in cultural portrayals of what goes on there. This isn't to say that necessarily is the cause, but you've by no means clearly demonstrated the lack of causal relationship you seem to think you have.
I think there is a difference between what girls are being told (by entertainment, by teachers, by parents, etc.) happens in engineering schools and what actually happens. The real point is that we can bend over backwards to fix whatever prejudices women encounter in engineering schools or as professional engineers and still accomplish nothing in terms of the disproportionate representation of women in our field.
In other words, if the problem is the environment within an engineering school, we should expect the trend to be a sudden, sharp change in female representation at the end of the first semester of the first year of college. Instead, we see poor representation in applications to engineering programs. I think that suggests the problem is earlier, and my own experience in engineering schools has been exactly that (my undergrad EE class had no women at all; in grad school, the vast majority of women I met were foreign, which might suggest something about our own culture versus others).
There is a difference, but there is also a relationship.
Consider a world (and ignore, for the moment, whether it corresponds to reality) where professional technical environments just genuinely are really awful to female employees. In that case, the teachers and parents are probably doing what's best for the individual girls (though potentially with some long-term tragedy of the commons). Would you condemn, there, the honesty of the well-intentioned messengers?
We should also consider an alternative fictional world, where women never have any issues in technical fields, and the cultural myth has arisen by whatever historical accident. In that case, I agree that it's quite legitimate to lay much of the blame at the feet of those perpetuating the incorrect myth.
Reality, of course, looks absolutely nothing like either hypothetical.
FWIW, my wife says she was turned off of technical studies after getting to Berkeley (having enjoyed physics in high school) by her impressions of the technical students on arrival.
I don't think anyone's saying men are to blame - this is a systematic problem. The important thing is not to blame someone, but to _fix it_. This post offers insight into the problem so people have a better shot at _fixing it_. So we can fight about who's evil or exactly what volume is ideal for talking about the problem, or we can
I don't like doing this, but "systematic" when you mean "systemic" is one of my pet peeves. Systematic things are deliberate, if the bias is intentionally done then it could be systematic. In this case, it's not clear that anyone is trying to drive women from the field so it's systemic, a property of the system, or culture in this case.
To discuss your comment, I didn't feel that the post brought any particular insight to fixing it, but rather was trying to encourage discussion. Sadly this post seems to have been flagged and is now buried on this discussion site. This problem is not one that we have a handle on yet, and discussion/analysis is key to determining why it exists. Of course, we can't discuss forever, at some point organizations and individuals need to act, experiment with different things and rectify the problems they can (and hopefully not shift them to darker corners).
Two days ago I was very tired. My grammar (particularly written) goes to shit at that point. If you're trying to nitpick someone who was nitpicking, I anticpated that so I rarely make these sorts of comments. I've just noticed a trend of "systematic" being used for "systemic", even though they have very different meanings. It confuses the discussion when vocabulary is used incorrectly like this.
Sometimes you can't, quotas aren't a useful solution. Check your recruiting approach. Are you recruiting from male dominated events? Are there more balanced forums or even female dominated forums you can also recruit from but haven't yet? Do you read the name of all applicants with their resumes? Try sorting applications without knowing the name, gender, race and see if perhaps you had an unintended bias in how you filtered them. Check your behavior. Do your female engineers end up as project tech writers and configuration managers more often than the men? Is that where they want to be or did you just happen to put them there? If so, why? Check the behavior of your staff, is there a guy who keeps hitting on the female staff or a particular person? I've seen this happen and several women leave before management acknowledged that his behavior really was a problem.
In the end, your 4:1 ratio may be fine, you may have hired the appropriate people for the position and there's no reason to fret. Same with ratios for other demographics. But recognizing that intended or unintended biases can be at play is important if we want to change STEM at large.
Lots of human groups are underrepresented in technology (africans, older people, latinos etc). Why are feminists the only ones that always make it to the frontpage (even superficial pieces like this one)?
Hypothesis one: Women are a majority of the population; Their absence is more surprising, and the number of people interested in changing it is higher.
Hypothesis two: There is a perception that the absence of women in tech is more a function of tech culture than broader socioeconomic issues (e.g. There's no racial equivalent of "Code Like a Pornstar")
Hypothesis Three: It's possible that the female gap is bigger than that of other groups.
Why do people instantly put up ideological blinders at the first mention of feminism in response to an interesting article?
I mean, do you find anything at all objectionable in what it says? Please share! Or a subtlety that it leaves out? Totally!
I agree with you that racial issues are underemphasized in technical communities, and in the same way we should use feminism as a framework for achieving the organizational and social goal of equality, we should try to do the same for race.
I find it objectionable that blindly applying feminist recipes in IT will have any effect. Feminism is not a framework but a set of ideologies, and even if we assume it is, applying it out of context, it is just stupid (e.g. a company claiming it is 'pro choice' in order to attract women). Most IT jobs are in countries where feminism already works for decades. Clearly you need something more than feminism to achieve total equality.
I would hazard to guess that is related to two factors: women are the largest group that are underrepresented; and it is harder to explain women's underrepresentation as a result of socio-economic factors.
No matter where you live, you can expect women to represent ~50% of the population. That makes it very easy to notice if there is a discrepancy, even if you work in a tiny office. To tell whether an ethnic/age group is, you first need to know the prevalence, then you need to have enough people that a discrepency is noticeable.
With a number of groups you can explain why a group is underrepresented by looking at socio-economic factors like their average income, access to technology, access to schooling, etc. For any socio-economic group, there should be (roughly) the same number of men and women in that group, so it can't be used as an explanation of the under-representation of women.
EDIT: I didn't notice that jailbot had already said what I said, but in a less wordy fashion.
The term 'equality' is frequently used there, but never defined, which seems odd for an article that revolves around performance metrics used as a metaphor for feminism.
The biggest issue I've come to see in this industry is the denial that there's even an issue. That's what makes sexism so hard to address.
You'll find no shortage of those who don't experience that marginalization deny its existence. Meanwhile, those who do experience it and try to share how they experience it are ignored or talked over.
It' focused on inequality along a particular axis and inherits from a historical tradition which has focused mainly on the disadvantages faced by one side of that axis.
By way of analogy, there are tools to optimize loops during compliation. This is part of the broader goal of optimizing software, but to call them simply "optimizers" and call it a day would be to pointlessly forfeit semantic bandwidth. Fixing problems requires getting specific. And yes, sometimes loops don't need optimization, and of course there are other things to take care of, but there's still value in talking about the specifics.
As a founder in tech field, I use a few steps to detect feminism,
1. If they have equal opportunities/equipments?
2. If the statements are bias based on other people instead of looking problem within themselves first.
3. Do they have the right/enough knowledge in the field.
In my experiences, Number 3 is very important. I never meet anyone with enough practice & knowledge about programming complains about gender problem. Stories I read is about people cannot write a single line of code but wants to be the executive/Project Manger.
The current title on HN of "Feminism is to equality as metrics are to performance" is far more interesting than the title at the blog of "Devops needs feminism", but it's never really elucidated.
The original title was indeed interesting. I expected a different case to be made, though - that much like metrics can be necessary to improve performance, feminism can be necessary to improve equality, but in both cases it's possible to focus too much on the means and not enough on the end. I'm not entirely sure how much I'd have agreed with such a case, but it's an interesting lens.
The author doesn't seem to know much about feminism (self-admitted); he seems to be using the first and best definitions he can find, find that that definition/decription resonates with him, and then tries to sell it. So anyone who believes in equality (and isn't an asshole) is a feminist. Okay. Then I'll similarly assert that everyone who believes in equal opportunity is a communist, that everyone who believes in freedom is a capitalist, etc. Now, everyone is at least superficially acquainted with these ideologies, so they won't simply take such assertions at face value, even if I say that 'there are many definitions and this is just my definition'. To assert that an ideology (or school of thought, or what have you) is about this and that, a handy 'definition' is not enough for me, personally. One should perhaps make an assessment based on what it's members do and say, such as bloggers, academics, etc.. Or restrict oneself to a particular wave of feminism. At least a more comprehensive description and/or analysis is in order if you want to correct others, than to simply cite a single definition from a single Wiki. That is just my opinion, OP.
The mistake here is viewing the entire system as simple, instead of emergent. Emergent systems are not usefully measured by simplistic top-down metrics.
You have one piece of code, yep, you set up some measurements and have fun with it. You have a thousand programs, running across a hundred different platforms? The idea that you can determine cause and effect by a simple top-down metric is a problem in itself. Yes, you may be able to determine that overall the system is not working as you would like it to be, and you may certainly decide that some kind of action is required, but that gives you no clue whatsoever what the required changes would be! In fact, by looking from the top-down in an aggregate fashion, it's even arguable whether or not your metric is the one to be optimized!
That's the difference between complex systems and simple systems. Stop over-simplifying. We all might be able to agree that some aggregate statistic is out of whack. Maybe. But that's a freaking long way from actually knowing anything about the problem or what to start doing to address it. Instead, we wrap it all up like that answer is straightforward, wave our arms around, get all emotional, and demand action. This is not a recipe for success, whether in complex systems of programs or complex systems of people.