News for hackers. Stuff that matters.
Re:Girls Who Code by crassus on Sunday December 29, 2013 @02:37PM (#6980905)
FWIW, the startup I was at seemed to have a soft affirmative action for females. They would reject males that didn't do much outside of college work, but would be willing to consider females with the same resume because "it would be nice to have more female coders".

Culture fit was about a modicum of friendliness. You could get rejected for culture fit by, say, looking away from your interviewer and mumbling to yourself. There could have been some great (and disadvantaged!) candidates with Eyeball Avoidance Syndrome + Tourette's that were rejected unfairly by the process, but so it goes.

The company was still 90% men in engineering, because that's what your talent pipeline looks like. I'm sure they were secret sexists, or something. Valleywag would write a scathing article about them.

In your example, I bet IBM was still predominantly male despite the anecdotal hiring of a few women that you mention.

Re:Girls Who Code by joe_the_user on Sunday December 29, 2013 @03:34PM (#6981218)
The thing about startups and bias is that if you have a multitiered informal hiring process, a little bit of biases can be invisible and can be multiplied over filtering stages.

The company may at one stage indeed "let's consider her" but unless the company's overall hiring is formally specified, unless your documenting and so keeping reasonably track of what you are doing, you may not know the way that biases are creeping your decisions.

Another thing about startups is they often involve a "join our company and our lifestyle" approach. That also means that you will windup with people like you.

Re:Girls Who Code by sunir on Sunday December 29, 2013 @09:29PM (#6982690)
Well, you can easily statistically measure the funnel of applicants to interviews to hired by gender and verify this claim. I doubt you will find the problem is multiplied hidden biases in the interviewing process.

Really there usually aren't enough applicants that are diverse on any dimension. Mostly because most applications are by direct referral of existing staff. That's legitimate. Eventually your company will grow big enough to hire a recruiter to look in new talent markets.

Re:Girls Who Code by crassus on Sunday December 29, 2013 @03:57PM (#6981352)
"Prove that you're not a witch" is a very old tactic - and it's the opposite of the modern standard of guilt.
Re:Girls Who Code by joe_the_user on Sunday December 29, 2013 @04:47PM (#6981563)
The "mismatch" in dialog about this stuff is perhaps telling.

One person says (essentially): "organization need to take systematic efforts to avoid bias in hiring".

The other person say (essentially): "you can't prove we're sexist, this is a witch hunt".

Re:Girls Who Code by smsm42 on Sunday December 29, 2013 @07:59PM (#6982449)
Unfortunately, we have a bunch of experience with statistically-based bias measures, and it often turns out to be exactly "prove you're not a witch" scenario. While in this particular case failure to prove probably leads to nothing but a blog post or a comment or two, in many other cases it leads to regulations and enforcement actions that can be very unpleasant for the target.

It can have some justifications where we know the bias exists. However, in this case we do not know it, so when people feel the onus of the proof put on them, they don't like it.

Re:Girls Who Code by hacker789 on Sunday December 29, 2013 @05:55PM (#6981877)
Not quite.

One person says, "We deliberately handle women with kid gloves. A under-qualified woman has a better chance than an under-qualified man."

A feminist activist responds, "But you still hire more men! Therefore, it's almost a given that you're biased against women in other ways. Fix it."

The original person says, "Wow. We just can't win with you people."

Re:Girls Who Code by joe_the_user on Sunday December 29, 2013 @07:23PM (#6982318)
If that happened, I could understand it. If you claim the thread above is summarized by that, you're hallucinating.

I simply said that bias can be invisible and it useful to have formal methods for catching it. I don't see myself as a "feminist activist" by any means.

I think the feminist activists who do sometimes uncritically toss around accusations of bias aren't really helping. But when I notice people reading my nuanced position and hallucinating a feminist rant, it increases my sympathies. It also doesn't speak well of people's abilities to see their biases (I wouldn't claim perfection for myself of course but the argument seems involve the claim that some people have no need for formal methods to correct their biases. I beg to differ, everyone needs that).

Re:Girls Who Code by belorn on Sunday December 29, 2013 @08:15PM (#6982495)
> but the argument seems involve the claim that some people have no need for formal methods to correct their biases. I beg to differ, everyone needs that

Demanding that everyone has a formal method to correct biases only provable in statistics, really do go back to the "Prove that you're not a witch" argument a few comments ago. The exact same proof can be found against different color of skin, names and clothes. It can be found in parents who has more than one children. Statistical proven biases exist everywhere.

Yet, a formal method should only really be needed once the bias is found to actually exist on a individual level. Everything else would be insane.

Re:Girls Who Code by nitrogen on Sunday December 29, 2013 @08:40PM (#6982560)
Yet, a formal method should only really be needed once the bias is found to actually exist on a individual level. Everything else would be insane.

Wouldn't a better approach be incorporating formal, rational methods into everyone's individual thought processes from the beginning? In other words, I believe adopting the overt rationality advocated by the likes of http://lesswrong.com/ would almost automatically correct a lot of societal problems caused by bias.

Re:Girls Who Code by lkrubner on Sunday December 29, 2013 @05:11PM (#6981688)
It is interesting that whenever this subject is brought up, someone will eventually introduce the subject of guilt. Can you articulate why you responded in this way? Do you feel that you have been accused of something? What exactly would the metaphorical equivalent of being a "witch" mean in this context?

I'll point out that we could have a conversation about diversity in hiring without ever introducing the subject of guilt.

This is a bit off-topic but I am fascinated about the exact reasons why some people react to conversations as if they have been accused of something. I think you might want to consider that nothing is useful is gained if you introduce the concept of "guilt" into a conversation where it is not needed.

I'll offer an example that has already been discussed on hundreds of blogs. You may recall in 2007 that John Kenzer interviewed Alex Payne? (I am sorry that the interview seems to be offline: http://www.radicalbehavior.com/5-question-interview-with-twi... but it is in the Internet Archive: http://web.archive.org/web/20070416091128/http://www.radical...) and Alex Payne offered some common sense observations about the difficulty of scaling Rails:

"Running on Rails has forced us to deal with scaling issues ... far sooner than I think we would on another framework. Once you hit a certain threshold of traffic, either you need to strip out all the costly neat stuff that Rails does for you ... or move the slow parts of your application out of Rails, or both."

You may recall that David Heinemeier Hansson's response was overheated and irrational. He said that Alex Payne was blaming Rails for all of the problems at Twitter. But Payne had never blamed Rails for anything, he merely talked about how they were struggling to make it scale.

(I am sorry to say that David's response appears to be offline now: http://david.heinemeierhansson.com/arc/000608.html , and the Internet Archive doesn't have it: http://web.archive.org/web/*/http://david.heinemeierhansson..... As a side note, let us all mourn how many important conversations get erased off the web.)

Many smart commentators pointed out that there was no need for David Heinemeier Hansson to introduce the concept of blame into that conversation. Alex Payne's words could have simply been taken as a constructive starting point for a larger conversation about how to scale Rails. But for some reason Hansson felt the need to frame the conversation in terms of accusations and guilt.

The same is true about this conversation, and your reaction. We can have a constructive conversation about increasing diversity in hiring without ever introducing the concept of guilt.

And yet, every time this subject comes up, someone feels the need to frame the whole thing in terms of accusations and guilt. The level of defensiveness on display is remarkable.

Re:Girls Who Code by theorique on Monday December 30, 2013 @09:40AM (#6984761)
Some possibilities:

- The implication, stated or not (usually not), is that some people (i.e. white men) hold their jobs in tech because they took a position that rightfully should have gone to a more qualified person of a different group (i.e. woman / racial minority). With the attendant implication that they aren't actually competent and that they only got their position through in-group affiliation.

- Men (white or not) who have worked hard in their education and their profession to be able to work and succeed in tech feel frustrated when their efforts are downplayed or dismissed because they are alleged to be 'playing the game on easy mode'.

- People (male or female, of diverse races and backgrounds) who believe in the value of hard work and have actually seen such work pay off in their profession - i.e. who have experienced meritocracy in action - are frustrated by those who claim that a meritocracy (however imperfect) does not exist and that all tech hiring is biased by some sort of 'old boys network' (which is an insult to women who did well, without whinging, by their own efforts in intellectual labor and networking)

Re:Girls Who Code by pc86 on Monday December 30, 2013 @10:36AM (#6984985)
Speaking only to your first point, I don’t think the implication is that the white man holds a job that a better qualified non-white-man should have gotten, I think the implication is often times that the white man should not have gotten the job because it would have been preferable to hire an equally qualified non-white-man solely on the basis of his or her non-white-mannedness. This often makes people defensive (I have been as guilty of this as anyone else, as a white man) because it may seem that they’re being told they are “taking” a job from someone who deserves it more not based on merit or even tangential career skills like networking or interview prowess, but just because they have a different skin color and/or chromosomes.
Re:Girls Who Code by mhaymo on Monday December 30, 2013 @05:10PM (#6987367)
Postulating "bias" in the hiring process does seem to imply that a non-deserving or less-qualified candidate was hired. Saying that being a non-white-male is itself a merit doesn't change that, and is also highly contentious.
Re:Girls Who Code by rada on Monday December 30, 2013 @01:49PM (#6986108)
The implication, stated or not (usually not)...

You missed the parent's point so entirely, it's as if you are an MRA bot posting the same old scripted comments no matter what actual discussion is taking place. He said that we could "have a conversation about diversity in hiring without ever introducing the subject of guilt" and that we don't need to "frame the whole thing in terms of accusations" and your immediate knee-jerk response is to list all these imaginary accusations that are being "implied". Can you just keep an open mind and consider the possibility that, as the parent says, none of these accusations are actually being made? (If you don't find the parent comment convincing enough, perhaps look at your own "not usually stated" qualifier).

Re:Girls Who Code by nostrademons on Monday December 30, 2013 @04:00PM (#6986910)
Theorique - to my eye, at least - was responding in kind to the academic arguments presented by lkrubner. He presents three possible explanations for the effect that lkrubner discusses. Nowhere in there is a value judgment, only three hypotheses.

A good rule of thumb for when a conversation has become personal and emotions are getting involved is when the word "You" comes up. Conversations that stay on a strictly academic level talk about the ideas involved, not the people who espouse those ideas.

Re:Girls Who Code by rada on Thursday January 02, 2014 @04:03PM (#7002273)
Ah, the tone argument... I Am Too Emotional, causing me to use Incorrect Words.

Except, here is what lkrubner said, emphasis mine:

The same is true about this conversation, and _your reaction_.

See how we were, in fact, having a thread where we all address each other personally? How you made up an arbitrary rule to discount my comment just because it made you uncomfortable?

Next time, check your own emotional state before jumping with with a lecture on someone else's. And try to argue on substance, not tone, please.

Re:Girls Who Code by theorique on Monday December 30, 2013 @05:51PM (#6987619)
Perhaps it's better to explain that as "the meaning received by some men".

As in, no specific criticism of white men may be intended, but some white men may experience a "call for diversity" as criticism, since they are well known to be the largest individual group in the tech industry.

Not saying that they "should" feel that way, nor that they are right or wrong for feeling that way, just that many do, and here are some possible reasons why.

Re:Girls Who Code by Goladus on Monday December 30, 2013 @09:09AM (#6984631)
> I'll point out that we could have a conversation about diversity in hiring without ever introducing the subject of guilt.

The concept of blame was implied with the comment (paraphrased) startup culture is bad for women. That is blaming language, even though the victim was general and the guilt lies with a vague notion of 'culture'.

If you want to avoid discussions of blame it helps to avoid judgmental language.

    "$VAGUE_CULTURE is $NEGATIVE_WORD [for $VICTIMS]"
Where $NEGATIVE_WORD is something like 'bad' or 'problematic' and $VAGUE_CULTURE is some poorly specified concept that everyone is just supposed to get.

It's nice when people don't jump to conclusions and talk about guilt and blame when it hasn't been made 100% explicit, on the other hand it's also nice when ideas are followed through to logical conclusions rather than left hanging for others take personally.

Re:Girls Who Code by dragonwriter on Monday December 30, 2013 @09:36AM (#6984738)
"Startup culture is bad for women" doesn't imply anything about blame, except maybe blame for failure to change now that that harm is observable. The existence of a harm doesn't imply that it was foreseeable in advance such that there is any moral culpability attached to it.
Re:Girls Who Code by Goladus on Friday January 03, 2014 @07:33AM (#7005128)
Yes it does, because everyone participates in culture and culture is an ongoing thing. Or rather: it can be interpreted that way quite easily so don't make a statement like that and then blame people for talking about guilt.

If you don't want people talking about guilt then avoid judgmental language ("bad" in this case, "harm" in yours) until it's very clear that a judgment is necessary. Having an arm amputated in a car accident is "harm", it's "bad". Is not being hired for a position really "harm?" Maybe it is, but unlike bodily injury such a determination is not so trivial to make.

Re:Girls Who Code by firebones on Monday December 30, 2013 @01:58AM (#6983450)
Regarding great conversations being lost to the ages: a great idea for a service is an instant record button that preserves these things, regardless of source. Think pastebin + storify combined. The internet needs an instant record button.
Re:Girls Who Code by leahculver on Sunday December 29, 2013 @02:58PM (#6981015)
Nope. IBM was >30% women engineers when I interned there in 2004/2005. About half the interns were women and there was plenty of racial diversity as well. My boss was a woman, my mentor was a woman, and frankly it was the most diverse place I have ever worked.
Re:Girls Who Code by PakG1 on Sunday December 29, 2013 @09:59PM (#6982778)
I have to say that I dislike it when someone says Bigcorp was like this, that is what Bigcorp's culture is. Having worked in several bigcorps, they are huge, diverse, and it's impossible for one employee to say that their experience is reflective of the entire company. There are differences from department to department, from team to team, and for the multinational bigcorps, from continent to continent. A warehouse worker for Amazon cannot say that they had the same experience as a merchandising agent, and we can't even start to compare those experiences with that of an AWS devops engineer.

When someone says, "My experience at Bigcorp was like this!", we should always tone it down to read it as "My experience on the whatsit team in the whazzat department at Bigcorp was like this!"

Sorry, just had to get that out there.

Re:Girls Who Code by icambron on Sunday December 29, 2013 @10:12PM (#6982818)
That was in response to:

> In your example, I bet IBM was still predominantly male despite the anecdotal hiring of a few women that you mention.

Responding to someone's completely unsupported generalization with an anecdote to the contrary is still a step up in the conversation. If you're genuinely interested in improving the rigor of the conversation, perhaps you should reply to the grandparent with, "how do you know?"

Re:Girls Who Code by frodopwns on Sunday December 29, 2013 @03:07PM (#6981067)
I think he was referring to a different time frame (1960s-1980s). But he didn't provide evidence so your objection may still be valid.
Re:Girls Who Code by crassus on Sunday December 29, 2013 @03:02PM (#6981035)
Google is reportedly over 30% women, too. I wonder if it is just something about startups - higher risk, lower guaranteed reward, worse training programs, higher pressure. The startup world compares well to the original California gold rush - a risk for a small shot at a high reward - and that was mostly male, too.

Also, keep in mind that it's a zero-sum game. If Google and IBM each hire 1,000 female engineers from top schools, that means that startups get less diverse.

Re:Girls Who Code by jfarmer on Sunday December 29, 2013 @04:42PM (#6981535)
> I wonder if it is just something about startups - higher risk, lower guaranteed reward, worse training programs, higher pressure.

This is explained equally well by inexperienced managers hiring people similar to themselves culturally, racially, and socioeconomically. Likewise, if I were a woman, I wouldn't want to work on a team with five dudes oblivious to their dude-dom.

Re:Girls Who Code by tonecluster on Sunday December 29, 2013 @09:57PM (#6982770)
Who in their right mind would want to work on a team of highly-intelligent, socially-challenged, culturally-homogeneous young men whose experience to date is primarily steeped in the casual misogyny, homophobia, and racism of MMORPG chat-channels; dorm-room bike-shedding; and adolescent dude-bro jokes?
Re:Girls Who Code by 3pt14159 on Sunday December 29, 2013 @10:21PM (#6982849)
The irony of being sexist in this HN thread is breaking my mind man.
Re:Girls Who Code by lmm on Monday December 30, 2013 @06:30AM (#6984154)
If they're good coders, sure. I can ignore work-unrelated stupidity, but if I have to work with someone incompetent at their job that becomes very unpleasant very quickly.
Re:Girls Who Code by webmaven on Wednesday January 01, 2014 @11:52AM (#6995453)
I'll just note that coding is actually more a collaborative activity than a solitary one, so the 'socially challenged' are not very likely to be 'good coders'.
Re:Girls Who Code by tonecluster on Monday December 30, 2013 @10:48AM (#6985033)
It becomes unpleasant very quickly regardless of the quality of the skills of the programmers.
Re:Girls Who Code by hacker789 on Sunday December 29, 2013 @06:33PM (#6982067)
Across all cultures (perhaps across all of history), women are more risk averse.

In fact, feminist activists didn't push to get more women into tech until tech was a higher paying, lower risk endeavor.

Only then did it become scandalous that young women were choosing different career paths (but interestingly, the fact that young women are earning more than young men and graduating from college in far greater rates than young men isn't scandalous).

Re:Girls Who Code by 001sky on Sunday December 29, 2013 @10:44PM (#6982913)
women are more risk averse

I think this is misleading. Men and women face different risks, and heterodox strategies are not indicative of very much. First, you need to be careful how you infer "risk taking" from "not taking the same bets", because the actual riks taken is a portfolio riks calculation which is blind. Second, you don't have any data to infer anyrthing about the quality of the risk taking they are in fact taking; that is in terms of actual/realize and even provability weighted expected returns. To give one crass example, a women could take a strategy of legal ownership of "high risk realized assets" through marriage. This is a "high-risk strategy", but it is also empirically true that many rich men are married.[1] Of course, the odds of success in this strategy are also not evenly distributed amongst women as a group, either. Another person could look at that and say that marriage to a rich person is a "risk avoidance" strategy...and again, this may or may not be true. Because wealth and genetic fitness need not correlate, and so your frame of reference on the purpose of strategy quickly turns into quite a bit more complex calculation.

[1] Marriage as a legal contract has a financial value; a derivative, with contingent claims on of the underlying (asset) value of couple's cumulative/aggregate incomes.

Re:Girls Who Code by jfarmer on Sunday December 29, 2013 @11:32PM (#6983050)
You and your complexifyin' aren't welcome around here, friend! All that nuance just makes our arguments much harder to make. You'd best take it elsewhere.
Re:Girls Who Code by alexmat on Sunday December 29, 2013 @11:58PM (#6983106)
I agree, "he talks like a fag and all his shit is retarded."
Re:Girls Who Code by jmagoon on Sunday December 29, 2013 @08:53PM (#6982599)
Do you have any evidence to back up your broad-brushed claims?

And who are these "feminist activist" strawmen(straw-women?) you have set up?

Re:Girls Who Code by newnewnew on Sunday December 29, 2013 @10:43PM (#6982911)
5 minutes of googling:

"MEN, WOMEN AND RISK AVERSION:EXPERIMENTAL EVIDENCE" - http://aysps.gsu.edu/isp/files/ISP_Ind_3.pdf

"Sex Differences in Everyday Risk-Taking Behavior in Humans" - http://www.epjournal.net/wp-content/uploads/ep062942.pdf

Reality fits egalitarian beliefs quite poorly.

Re:Girls Who Code by jfarmer on Sunday December 29, 2013 @11:28PM (#6983046)
You've obviously made a serious study of this and that's why you have such justifiably strong opinions on the matter. Can you do 10 minutes of googling next time and share more? Or maybe 20?! Think of how informed you'd be after 20 minutes!
Re:Girls Who Code by mistermann on Monday December 30, 2013 @10:22AM (#6984928)
If you wish to make an apple pie from scratch you must first invent the universe.

It's pretty difficult to have a serious conversation if you have to fully define and prove every single piece of content in a comment.

Common sense is getting to be pretty rare around here.

Re:Girls Who Code by jfarmer on Wednesday January 01, 2014 @01:56PM (#6995990)
> If you wish to make an apple pie from scratch you must first invent the universe.

There's plenty of room between "justify everything from first principles" and "perform an ad hoc 5-minute search of the web for research that confirms what I already believe." I'd also say, the closer one is to the former, the more justified one is in feeling certain about their beliefs.

> It's pretty difficult to have a serious conversation if you have to fully define and prove every single piece of content in a comment.

That's good, because nobody here is advocating that!

> Common sense is getting to be pretty rare around here.

Well, as they say, "Common sense is nothing more than a deposit of prejudices laid down by the mind before you reach eighteen."

What's "common sense," here? That women are more risk-averse? I disagree, at the very least until one defines "risk" and "risk-averse" very precisely. My "common sense" tells me otherwise. Shucks. Ain't that the problem with "common sense?"

Re:Girls Who Code by mistermann on Sunday December 29, 2013 @11:07PM (#6982982)
I think part of the reason these discussions never get anywhere is because of blatant dishonesty in discussions. You actually think there is no "feminist activist" movement?
Re:Girls Who Code by jmagoon on Monday December 30, 2013 @03:32PM (#6986737)
I don't, and I never made that claim because it's insane. I object to the idea that "feminist activists" "didn't push to get more women into tech until tech was a higher paying, lower risk endeavor."

There's a claim "women are more risk averse", and another claim "feminist activists exist", both of which are feasibly true, that do not lead to general conclusion that "feminist activists did not push to get more women into tech until it was a higher paying, lower risk endeavor". Which is a broad, unsupported argument, for which the data directly contradicts:

http://blogs.computerworld.com/it-careers/21993/women-comput...

Re:Girls Who Code by mistermann on Tuesday December 31, 2013 @12:24AM (#6989161)
I must be confused or misinterpreted you.

"And who are these "feminist activist" strawmen(straw-women?) you have set up?"

I took that to mean (generally) that the idea that there is such a thing as a legitimate feminist activist is nonsense - that in reality any reference to one is as part of a straw man argument. Not what you were saying?

Re:Girls Who Code by jmagoon on Tuesday December 31, 2013 @10:28AM (#6990889)
What I meant was that he was characterizing all feminist activists as wanting or doing X (X being unsupported, anyways), which seems to me to be an unfair generalization and an easy to knock down, stereotypical villain.

I should have clarified in the original post, apologies.

Re:Girls Who Code by rodgerd on Monday December 30, 2013 @04:07AM (#6983774)
> women are more risk averse.

When was the last time you did something as risky as get pregnant?

Re:Girls Who Code by x0x0 on Sunday December 29, 2013 @03:26PM (#6981170)
google may be 30% women overall but I would be shocked if that where true of engineering; Rachel of rachel by the bay definitely didn't have that experience
Re:Girls Who Code by judk on Sunday December 29, 2013 @04:49PM (#6981569)
30% is probably including sales org, it is high for engineering. Anyway, consider the difference between 2-3 women of 12 people in an startup, vs 200 of 1000 in a big company, where women may cluster on some teams, or have "dotted line" relationships outside their official hierarchy.
Re:Girls Who Code by dspillett on Monday December 30, 2013 @05:33AM (#6984008)
> The company was still 90% men in engineering, because that's what your talent pipeline looks like.

Same here. I think we've hired all the women who have applied for Dev jobs as we expanded though not because of any positive discrimination (as far as I know, though hiring/firing is out of my remit). All two of them.

I get the impression that women are put off a career in the sort of technical role we need (or, to look at it the other way around, are drawn to other things) fairly early in their education. Those that stick with it are determined so tend to end up making the effort and being damn good, but the rest end up thinking it isn't for them for more so than boys in a similar position. A lot of that is going to be cultural (the "boys toys" attitude mainly) but I see this falling away as personal technology has become much more ubiquitous in the last decade or so with everyone having/wanting flashy phones, tablets, and other techie toys. The proportion of my younger family members' female friends who are specifically/actively interested in a technical profession seems much higher than was the case when I was that sort of age about 18 years ago (though game designer and game tester are the main dreams there, I'm not sure how to tell them about the disparity between their expectations and the level of stress people are under in that part of the industry!).

> I'm sure they were secret sexists. Valleywag would write a scathing article about them.

I think we are pretty much not sexist, or anything-else-ist for that matter, but in a way that might be a problem for some. I don't know if this holds industry wide, but our sense of humour can be quite non-PC though it is applied fairly: all stereotypes (gender, age, country, size, religion, diet, hair, ...) are fair game for a joke and we don't tend to reign it in for any particular group or individual (though we aren't completely heartless in that regard). No harm is meant and no-one has thus far taken offence but I imagine there are some sensitive souls out there who would find it makes for an environment uncomfortable to work in (so one of these days it might cause problems if someone goes too far and someone does take significant offence, I can certainly imagine circumstances where that might happen).

Re:Girls Who Code by mathattack on Monday December 30, 2013 @07:23AM (#6984291)
IBM may have been, but women of that era made it to CTO and CEO. (IBM has had other issues so I am not defending)