News for hackers. Stuff that matters.
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.