News for hackers. Stuff that matters.
Re:Girls Who Code by lkrubner on Sunday December 29, 2013 @02:02PM (#6980746)
One fascinating aspect of this is how bad the post 1990 startup culture has been for women. There was something about those big, boring corporations of the 1970s and 1980s that actually gave female hackers more acceptance than what startups have offered.

You can see female interest in programming change in the charts on these pages:

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

Note that those graphs show raw numbers, not a percentage of the population -- if you adjust for the growing population, female graduation rates in computer science peak in the 1980s. As it says in the text:

"As a share of all CS bachelor's degrees granted that year, females had slipped almost 10 points, from 37% in 1984/1985 to 27% in 2003."

A family anecdote: my mom was working on her Phd in urban planning back in the 1970s and her advisor said to her "You know, in the future, many of these issues of traffic and resource allocation will be resolved through computer simulations, so you should learn to program." My mom thought that was a good idea so she took some classes and learned basic programming. She does not recall feeling like an outsider in those classes: the computer field was still new and felt wide open.

Nowadays a lot of startups talk about the need for "culture fit". This tends to limit the diversity of the gender and race and class of who is hired. For contrast, consider people like Evelyn Boyd Granville, and her acceptance at IBM.

http://en.wikipedia.org/wiki/Evelyn_Boyd_Granville

Here on Hacker News we also discussed the story that Raganwald posted, about another black woman at IBM, though that article is now offline:

http://raganwald.posterous.com/a-womans-story

If IBM applied a filter of "culture fit" then these women would not have been hired. But IBM, and many of the big corporations in the USA, followed very liberal policies that promoted diversity in the work place.

There were some startups from the 1950s and 1960s that broke new ground in terms of diversity. Ray Kroc built up a small startup called McDonalds and in a quiet way he made feminist history in his treatment of June Martino. She was initially hired as the bookkeeper, but she was later entrusted with vast responsibilities and finally, in 1965, when McDonalds went public, she was given shares in the company, exactly like any other cofounder of a startup. This was apparently the first time in history that a woman was treated as a real cofounder and given stock.

http://en.wikipedia.org/wiki/June_Martino

If you look at the numbers, it seems clear that the emergence of the tech-based startup scene, in the 1990s, changed things for women. The startups have not emphasized hiring diversity. The startups tend to emphasize culture fit, and they were doing so even before that phrase came into existence. Why this should be, I am not sure. There have been startups in the past that have emphasized diversity in hiring, so I am not clear why the current generation of startups cannot do so. But what is clear is that it is not a priority for them. The big and boring corporations of the past did a better job of creating spaces for women in tech.

Edit to add: to avoid being overly innocent, we should note how much the talk of "culture" is sometimes a smokescreen to hide power dynamics. Shanley Kane said "In Silicon Valley, and the tech industry in general, a lot of people were giving these talks about what their culture was and it was really superficial and focused on the privileged aspects of the company like free food and massages." Here on Hacker News we have already discussed the post "Google's 'free food' is not free" but it is worth remembering how much the talk about "culture" is just a negotiating tactic.

http://rachelbythebay.com/w/2012/01/21/notfree/

Re:Girls Who Code by yummyfajitas on Sunday December 29, 2013 @03:14PM (#6981100)
But IBM, and many of the big corporations in the USA, followed very liberal policies that promoted diversity in the work place.

A meritocracy based on raw intelligence and skill (measured by standardized testing) is not exactly what people mean today when they discuss "promoting diversity". In fact, nowadays people typically criticize such practices as inhibiting diversity [1].

As for culture fit, it's a complicated thing. There are some culture issues that can be a real problem - for example, my company really can't deal with people who don't believe in "let data make the decision". Similarly, there are companies out there which highly value civility and team spirit over correctness - my "this is broken, here is why" style would not work for them.

A lot of culture fit is just "do I think these guys are cool" silliness, but don't let that overshadow the fact that culture matters.

[1] http://ashedryden.com/blog/the-ethics-of-unpaid-labor-and-th... http://flosspols.org/deliverables/D16HTML/FLOSSPOLS-D16-Gend...

Re:Girls Who Code by glesica on Sunday December 29, 2013 @09:24PM (#6982677)

  > A meritocracy based on raw intelligence and skill (measured by standardized testing) is not exactly what people mean today when they discuss "promoting diversity".
Well sure, but largely because the standardized tests are all biased against women and/or minorities. [1] Aside from that, what exactly is a "meritocracy"? What does that mean? You have to define it pretty carefully. HN is full of posts about making social connections to get what you want, so is it a sign of merit if someone has lots of social connections and can therefore get jobs/funding? I mean, is it common for startups to actually administer intelligence/IQ tests to their prospective hires before interviewing them? Be careful when making claims about "merit" because it can be defined in many different ways, and most of them are pretty unappealing once they are spelled out.

[1] https://encrypted.google.com/search?hl=en&q=standardized%20t...

Re:Girls Who Code by theorique on Sunday December 29, 2013 @10:26PM (#6982863)
Well sure, but largely because the standardized tests are all biased against women and/or minorities.

IQ tests - which are pretty well normed across cultures if you use the right ones - tend to turn up the same patterns over and over.

IQ tests (or their proxies) are useful ways of testing general cognitive fitness and ability and anticipating on-the-job performance and learning (see, e.g., http://www.udel.edu/educ/gottfredson/reprints/1997whygmatter... )

Some minorities seem to score higher than the mean (in some cases, up to one standard deviation higher) and some minorities tend to score lower. This is less about bias and more about measured genetic differences. (see, e.g., http://www.news-medical.net/news/2005/04/26/9530.aspx )

And further, it seems as though women are no slouches in the IQ game: http://www.dailymail.co.uk/news/article-2173808/Women-overta...

Re:Girls Who Code by glesica on Sunday December 29, 2013 @10:49PM (#6982929)
So then why don't startups hire based on the results of IQ tests, isn't this a meritocracy? You actually made my overall point stronger, because you demonstrated that this community clearly doesn't define "merit" to be "raw intelligence". It is a much, much more nuanced concept and it includes, I suspect, a large number of characteristics that are heavily influenced by gender, culture, and class. When we say "merit" we do not simply mean "how smart are you?", if we did, then according to your evidence, more companies would use IQ tests for screening potential employees.
Re:Girls Who Code by yummyfajitas on Monday December 30, 2013 @02:44AM (#6983589)
Unless I plan to teach someone how to code, I also need to know if a person can code. In the era lkrubner was describing (the IBM/mainframe era), no one could code due to the small number of people with a mainframe in their basement.

Nowadays we hire people who already know how to code - I don't have time to teach someone to code. That's why I'm a big fan of github-as-resume. I want you to write code to make my company money so show me your code. But since women choose not to write open source, this form of work-sample test is criticized as discriminatory as well.

Also note that certain large meritocratic institutions (trading desks, some tech firms) do hire more or less on IQ. They can't actually give an IQ test themselves due to Griggs vs Duke Power so they outsource it to elite colleges instead. That's basically what is happening when they say "must come from a top school".

Re:Girls Who Code by theorique on Monday December 30, 2013 @07:20AM (#6984278)
In companies I worked for in the past, I definitely had to do IQ-ish tests such as puzzles and brain teasers. Many people in the tech industry have encountered this.

The cultural mythology of Google (and earlier, Microsoft, when they were the ascendant, 800-lb gorilla) was about their puzzle based interviews, and how they didn't care about your specific skill set but only raw intelligence. (We can debate about whether that was the best way to select and hire people, but I don't think there's much dispute that this was something these companies did.)

It's probably worth noting that the companies that used the brain teasers and IQ-proxy tests also did a "cultural fit interview" - basically, trying to answer honestly the question "would I be cool with spending 8 hours a day working with this person, or would I be seeking ways to kill myself?"

Re:Girls Who Code by glesica on Monday December 30, 2013 @06:03PM (#6987692)
The problem is that those tests probably DO have cultural or gender biases. GP was pretty specific about the fact that only SOME intelligence tests have been shown to be effective and free of cultural and gender bias. So then we're back to my original comment.
Re:Girls Who Code by theorique on Wednesday January 01, 2014 @08:12PM (#6997651)
I agree that an a in-house puzzle, brainteaser, and math test would probably be shown have some biases if it were analyzed according to the same processes that are used to analyze IQ tests and other psychometric tests.
Re:Girls Who Code by erichocean on Wednesday January 01, 2014 @09:35AM (#6995053)
So then why don't startups hire based on the results of IQ tests, isn't this a meritocracy?

That specifically is illegal in the United States.

Corporations are forced to use proxies instead, such as SAT or ACT scores, or things keyed to that, like college admissions.

Re:Girls Who Code by Crito on Sunday December 29, 2013 @11:27PM (#6983042)
> So then why don't startups hire based on the results of IQ tests, isn't this a meritocracy?

In the US, doing that is a decent way to get sued.

'tokenadult has a standard comment (he's made it many times with various revisions/updates) on this topic that you should read: https://news.ycombinator.com/item?id=6584957

Re:Girls Who Code by yummyfajitas on Monday December 30, 2013 @02:32AM (#6983548)
The few links provided by your google search do not back up your claim of bias - they repeat the same vague assertion as you but provide no evidence. If you have evidence of this claim please be more specific about presenting it.

I also didn't claim any startups use IQ tests.

The point I was making is that what lkrubner described as "very liberal policies that promoted diversity in the work place" (namely, assessing ability via objective, quantitative means rather than subjective interviews) is now criticized by folks like yourself as anti-diversity. The legal precedent set by Griggs vs Duke Power and related legal cases makes it legally problematic.

Merit, BTW, is defined as "whatever will make my company the most money". In some roles it does involve social connections.

Re:Girls Who Code by glesica on Monday December 30, 2013 @11:22PM (#6988929)
If "objective" and "merit" are defined as "upper-middle class white men" then don't talk about IQ tests, just say what you mean.

My point is that you can couch what goes on in whatever language you like, but if you don't care about social justice, then just say so and stop pretending that what you are doing is actually the "real" social justice or is somehow "natural" (for some weird, pseudo-genetic definition of "natural").

This is the same complaint I have about a lot of "capitalists". They like to talk about how the market will yield these socially optimal outcomes, but to listen to them tell the story, the market ALWAYS yields whatever is PC at the time. The truth is that the market is devoid of morality or values, and maybe that's fine, but don't lie about it. If the system you support has property X, but not property Y, don't pretend it has property Y just because property Y is easier to advocate for, be proud and stand up for your belief in property X!

Hiring is biased toward white men for a variety of reasons. If you are OK with that, then fine, say so. You didn't cause the historical problems women and minorities have had, so there's a reasonable argument to be made that you shouldn't have to pay for them. I, personally, would rather make less money but help equalize historical inequities, but that's just me. I also buy single-fly toilet paper because I think it is less wasteful, but I don't go around yelling at people who buy two-ply, that's their business. But don't pretend that by some weird contortion of logic and the rules of the universe hiring white men is "right". It's just more profitable because of the historical oppression of people who weren't white men. So say so. End of story.

Re:Girls Who Code by yummyfajitas on Tuesday December 31, 2013 @05:08AM (#6989853)
"Objective" means "different people applying the procedure will get the same answer". This is a property held by standardized tests and carefully defined interview processes. "Merit" is defined as "what will make me the most money".

I don't know why you believe I'm pretending to do "social justice". I'm not. I'm trying to make money, just like IBM in the mainframe era. Hiring based on coding ability is profitable because a software business is about turning code into money, it has nothing to do with "historical oppression".

Incidentally, I'm opposed to "social justice". Social justice is based on the premise that certain subsets of humanity [1] deserve special rights (mostly statistical equality), but the other 2^{6 billion} subsets of humanity do not.

If that's a moral axiom I don't share it. If it's derived from some other moral principle, I have not heard a coherent derivation [2].

(To fully grasp the philosophical issue I have, explain why you care about "women and minorities", but not "children of murder victims and people who's SSN ends with 3847".)

[1] Typically women, lgbt, blacks, hispanics, but not asians.

[2] The closest I've ever heard is basically "everybody cares about race/gender/lgbt so we do too".

Re:Girls Who Code by reefoctopus on Tuesday December 31, 2013 @03:34AM (#6989644)
>Well sure, but largely because the standardized tests are all biased against women and/or minorities

I can't tell whether or not you are being sarcastic.

Re:Girls Who Code by anthonyb on Sunday December 29, 2013 @11:12PM (#6982993)
Friendly reminder that "meritocracy" is intended as an anti pattern, in the same way that waterfall is.

Edit: here's a thoughtful piece on the term and its implications, from the original coiner of the term: http://www.theguardian.com/politics/2001/jun/29/comment

Re:Girls Who Code by stcredzero on Sunday December 29, 2013 @03:39PM (#6981252)
> The startups have not emphasized hiring diversity. The startups tend to emphasize culture fit

Basically, "culture fit" is the same thing that the characters of Mad Men look for when they hire, just modulo a different culture. We can't get rid of this aspect of human nature, but we can make it more about rational and objective subjects and less about arbitrary cultural baggage. Basically, less smarmyness/arrogance, more humility, and more insight.

Smarmy and arrogant Ivy-leaguers from the Mad Men days couldn't see their own arbitrary bullshit. It's hard to see one's own arrogant bullshit, especially when you're constantly telling yourself how you're an elite in a meritocracy. Take it from a formerly smarmy and arrogant Ivy-leaguer. If you're a 20-something and think you're immune, you're a prime suspect.

Re:Girls Who Code by VLM on Sunday December 29, 2013 @05:18PM (#6981711)
"As a share of all CS bachelor's degrees granted that year, females had slipped almost 10 points"

This line of reasoning seems to assume that virtually all CS grads go into "post 1990 startup culture" companies. I suspect that nationwide, fresh grads going into startups is a rounding error.

I'm not disagreeing with the conclusion, just claiming the facts in support of it are not a good fit.

Something cultural that I could match up to declining female grad rates would be the stockholm syndrome-like popularity of the programming death-march meme, see videogame programmer lifestyle etc. Maybe women are smart enough to avoid that particular form of stupidity and thus avoid the field, but men are too dumb, thus maleness ratio increases.

Re:Girls Who Code by klipt on Sunday December 29, 2013 @06:24PM (#6982015)
> Maybe women are smart enough to avoid that particular form of stupidity and thus avoid the field, but men are too dumb, thus maleness ratio increases.

To quote Philip Greenspun:

> I've taught a fair number of women students in electrical engineering and computer science classes over the years. I can give you a list of the ones who had the best heads on their shoulders and were the most thoughtful about planning out the rest of their lives. Their names are on files in my "medical school recommendations" directory.

http://philip.greenspun.com/careers/women-in-science

Re:Girls Who Code by ericedge on Sunday December 29, 2013 @02:17PM (#6980816)
To some extent I wonder if the difference between the two environments is the acceptance of more junior engineers into the ranks. Even the original link suggests that female coders need to have the same skills as the male coders in order to succeed in the field, whereas one of the main bullet points for Carnegie Mellon's success was specifically encouraging students with no prior experience to join the program:

http://blog.play-i.com/carnegie-mellon-study-on-gender-and-c...

But how often in web engineering do you see postings for junior employees? Everyone wants someone who already has experience, the more senior the better. How do we get more people of any diversity to work at our companies if there are no entry-level positions in the field?

I think some of this might arise from the fact that web engineering is still a relatively new field. People making staffing decisions feel like they're taking on enough risk as-is, and don't want to take on the additional burden of training up junior engineers.

But if we don't train them, gaining diversity will be much more difficult, and we may some day find ourselves with a quickly-dwindling pool of experienced engineers to draw from.

I'm not sure we're there yet, but when we reach that point, already having a solid training program in place at a company will be an incredible market advantage. So we might be shooting ourselves in the foot by not starting those training programs now.

Re:Girls Who Code by ama729 on Sunday December 29, 2013 @02:29PM (#6980870)
> But how often in web engineering do you see postings for junior employees? Everyone wants someone who already has experience, the more senior the better. How do we get more people of any diversity to work at our companies if there are no entry-level positions in the field?

Unfortunately, it's true in most field, it's extremely rare to find an ads that doesn't ask for a diploma and job experience (it didn't ask for experience, but I saw an ads where they asked for a diploma in a call center position...)

Re:Girls Who Code by gfodor on Sunday December 29, 2013 @02:17PM (#6980815)
"Culture fit" is a vague enough term to not really be able to say much about it. Are there companies who use it as a way to hide behind discrimination? Sure, almost certainly. But in my past experience the amount of times we rejected a candidate due to "no culture fit" was quite low and was for reasons that were of the flavor: "this person sounds like they totally caused drama in their old workplace" or "this person admitted to bending the rules in a way we find ethically dubious" etc. In other words, there are certainly alternative criteria for "culture" fit that are legitimate things to consider and are not discriminatory.
Re:Girls Who Code by tptacek on Sunday December 29, 2013 @02:39PM (#6980914)
This speaks to how deranged mainstream software hiring practices are.

To wit: take a bunch of practitioners more or less at random and arrange to have them serially interview candidates. Apply virtually no structure to the interviews themselves; most of those practitioners will be free to generate their own questions, and if any guidance is given at all, it will usually take the form of "assess the candidate's abilities along axes X, Y, and Z" (for "X" of the form "Rails" or "Django" or whatever, &c). To that haphazard scheme, strongly imply that those practitioners are not merely expert at assessing the abilities of others (something that does not follow from the mere observation that the practitioners themselves are competent in the field), but also psychologists capable of extracting from a 45 minute adversarial interview the "culture" and mentality of candidates who are so nervous and upset from being judged by hostile strangers in this crapshoot process.

Software hiring is widely regarded by hiring managers as a nearly random process; at best, at savvy companies, the house might have an edge over time. And the cost of that edge is a system that is inhumane to virtually everybody, with the possible exception of a small elite of sought-after developers.

Re:Girls Who Code by andrewljohnson on Sunday December 29, 2013 @02:53PM (#6980994)
How does Matasno's hiring process work? I don't think I've heard you comment on hiring except to say everyone does it wrong.

In my company, we've hired everyone based on remote/part-time work, and paid tryouts. This seems to work well, but I don't feel like I can hire people who currently have full time jobs this way. I'm not sure how best to judge candidates who I can't observe working, besides a standard battery of technical interviewing and a lunch with the team.

Re:Girls Who Code by tptacek on Sunday December 29, 2013 @03:07PM (#6981062)
I'll try to condense it as much as possible, and add the caveat that our process is imperfect:

1. Build outreach programs that are open-enrollment and broadly targeted (for instance, the crypto challenges aren't targeted at security industry events).

2. Explicitly overcommunicate the whole hiring process to candidates up front and sell the job, before attempting to screen. Actively try to correct for the adversarial nature of the process.

3. Drastically reduce the impact of phone screen interviews.

4. Administer standardized work-sample tests to all candidates regardless of previous experience; those tests have quantifiable outcomes (which we record).

5. Administer standardized on-site interviews with quantifiable outcomes (right now, they're "exercises", but their form might change over the long term).

The only point in our process where interviewers have a lot of flexibility in terms of what they do is the phone screens. We use the phone screens to generate predictions for how candidates will do on the rest of the interview, but we don't screen with them. (We would if the phone screen revealed a candidate to be a crazy person or a jerk, but I don't think that has ever happened).

So far, the things that have been most noticeably successful for us:

* Standardized, quantifiable results that allow us to generate a model of what a successful candidate actually does, rather than a gut feeling based on how well they answer questions, or how "confident" they are, or how "well spoken", or how impressive their resume.

* Outreach to the industry as a whole, not just to the small sectors of the industry we believed a-priori would generate the best candidates. Some of our best people have come essentially "out of nowhere", and recognizing that fact I'm especially interested in optimizing for that.

It is thrilling --- best word I have for it --- to find someone who's had no relevant job experience, hire them because they do unexpectedly well on a series of quantifiable metrics, and then see 6-9 months later that they are, say, showing us how to use BKZ lattice reduction and fourier transforms to exploit elliptic curve nonce biases.

Re:Girls Who Code by yummyfajitas on Sunday December 29, 2013 @03:57PM (#6981353)
This sounds like a vast improvement over most normal hiring processes. A question though - how do you avoid legal liability from (4) and (5) in the event that they cause a disparate impact (see Griggs vs Duke Power, etc)?
Re:Girls Who Code by tptacek on Sunday December 29, 2013 @04:05PM (#6981389)
I don't think about it at all, and for good reason: nothing that our process does could possibly be more risky than the crapshoot process other companies use. To wit: I know for a fact that my process isn't going to be dumb enough to ask a woman whether she's going to be able to manage her child care responsibilities and still be able to answer emergency work calls.
Re:Girls Who Code by yummyfajitas on Monday December 30, 2013 @03:22AM (#6983674)
The danger comes from the fact that courts generally give deference to ad-hoc processes, whereas systematic processes are inherently suspect. That's why interviews are fine but IQ tests are legally suspect.

As another example in this general line of thought, compare Grutter v. Bollinger and Gratz v Bollinger. Point-based racial discrimination is illegal, but "holistic" "individualized" processes where race is just a "plus factor" are legal. (Only discrimination in favor of non-Asian minorities, of course.)

I agree that this legal doctrine is insane.

Completely tangentially, since you mentioned relevant questions which are illegal to ask, I'd love to see an economic analysis of this topic. Specifically, the classical Akerlof lemon market paper assumes a complete inability to measure quality. But in the hiring market there are only a few dimensions for which one is unable to measure quality. That complicates the analysis significantly, so I'd love to gain some intuition on the topic.

Re:Girls Who Code by temphn on Sunday December 29, 2013 @05:59PM (#6981892)
How many women and non-Asian minorities does Matasano end up hiring with that process?
Re:Girls Who Code by defen on Sunday December 29, 2013 @04:30PM (#6981478)
The point of Griggs vs Duke Power is that a work sample test would probably need to be "reasonably related" to the job at issue, if it has a disparate impact on minorities (meaning minorities pass at a lower rate). I have no idea how one proves in court that a test is "reasonably related", because I'm not a lawyer :-)
Re:Girls Who Code by tptacek on Sunday December 29, 2013 @04:39PM (#6981517)
Yeah, I'm familiar with it; my point is that the ad-hoc procedures companies use in place of work-sample testing are much more perilous. I've been a witness to more than one legal action that resulted from them.
Re:Girls Who Code by defen on Sunday December 29, 2013 @04:47PM (#6981562)
I see. For some reason I read your statement as being about disparate impact rather than ad-hoc hiring procedures.
Re:Girls Who Code by WalterBright on Sunday December 29, 2013 @02:58PM (#6981016)
All decision making processes with a human in the loop are going to be random, arbitrary, capricious, etc. But inhumane? about a job? It actually seems very humane. After all, only a human can look past the rules and see that a candidate is someone special that would be great for the company despite not matching the criteria.

Would you rather be selected for a job by a computer that follows inflexible rules embedded in software? That would be inhumane.

Re:Girls Who Code by tptacek on Sunday December 29, 2013 @03:09PM (#6981080)
I am telling you that after watching the Nth person go through an on-site interview process that we had already actively tried to program as positive and encouraging, and seeing them physically shaking in the conference room, and then thinking back on the last time I had needed to endure a job interview and how I felt, that yes, the process is inhumane. It demands of candidates that they endure a deeply uncomfortable process of being judged in 45 minute snapshots by strangers who often by all appearances seem to have rejection as an overt goal.

Your last question presents a false dichotomy and so I won't answer it.

I am, incidentally, a fan of your comments on HN. I'm just not interested in an argument where we're both going to be talking past each other.

Re:Girls Who Code by ericd on Sunday December 29, 2013 @04:42PM (#6981534)
Yeah, I completely agree - I absolutely hate interviews, to the point where I would prefer to do a large amount of work on alternative methods over a full day of interviews.
Re:Girls Who Code by gfodor on Sunday December 29, 2013 @02:43PM (#6980928)
Is it the case that you do not screen candidates based upon any other criteria than skills-based assessment in other fields? That assumes people are robots. I don't care what field you are talking about, people are always going to screen for "culture fit", since it can be defined to mean anything you want. It's "can I work with this person", "does this person seem trustworthy and honest", etc. The only difference is that it some places acknowledge this aspect of hiring, give it a name, and try to objectively assess it openly.
Re:Girls Who Code by tptacek on Sunday December 29, 2013 @02:48PM (#6980959)
You can complete the sentence "people are always going to ________", especially as regards software hiring, with all sorts of crazy shit. Hiring is broadly and deeply fucked up. Very few organizations do it especially well. The median companies does it abysmally. But we don't notice, because we develop other systems to compensate for how bad we are at getting the right people in the door.

That's my point, why I bring up how bad hiring is. "Widespread best practice" in hiring does not imply effectiveness. Most companies are terrible at hiring. They just get away with it because other aspects of those companies are good enough to compensate.

Re:Girls Who Code by philwelch on Sunday December 29, 2013 @03:00PM (#6981022)
"Culture fit" is a terrible word for it. What you do is you explicitly lay out the principles you expect people to follow and conduct behavioral interviews to find times they've followed those principles in the past.

Here's an example: let's say you're a typical startup, and you need to move fast. You need to think fast and you need to act fast. Let's say you've made the decision to hire people around that principle. You can ask someone about how they've coped with short deadlines, or to tell you about a time they had to get a lot done in a short period of time, and you judge them based on their responses to your questions.

Generally there will be a number of different principles, and there are also ways you can overdo them, but you want to decide on the right balance and the right mix and then conduct behavioral interviews to measure candidates against that.

The wrong way to do it is to make subjective judgments like, "I want to work with this person" or "I can really have a conversation with this person".

Re:Girls Who Code by bermanoid on Monday December 30, 2013 @01:23AM (#6983345)
If someone rubs you wrong personally, why in the world would that not be relevant, especially on a small team? Sure, you don't have to be besties or anything, but being able to at least converse with someone makes any work relationship go a lot smoother, and inability to do so can cause serious problems.

I'd never let a good culture fit override a poor technical interview, but I've seen the consequences of hiring a brilliant programmer that happens to be an asshole, and it's not pretty. Am I misinterpreting what you're saying, or do you really think social skills should be entirely ignored when it comes to hiring?

Re:Girls Who Code by philwelch on Monday December 30, 2013 @01:48AM (#6983420)
> If someone rubs you wrong personally, why in the world would that not be relevant, especially on a small team?

Because business decisions should be made based upon facts and data, not based upon hunches and gut feelings. Going with your gut basically means throwing out the data and letting all of your personal biases decide the matter, consciously or unconsciously.

If it's a question of being able to work with others, then you can develop principles and behavioral interview questions around what you want your coworkers to be like. That's a bit of a pain in the ass, but empiricism was always more of a chore than just following your gut instinct.

Re:Girls Who Code by bermanoid on Monday December 30, 2013 @02:45AM (#6983591)
Ok, I can buy that - your point is that you should be attempting to get an unbiased estimate of how well someone works on a team, not that it shouldn't matter. Totally reasonable. Much more difficult, but a worthwhile goal.

I feel like it might be almost impossible to remove gut feeling from the equation alogether, though, since a lot of the problems that wreck teams really do come down to "X really doesn't like Y's personality". At some level, isn't a negative gut feeling expressed by one of your team members as valid a data point as you can get to predict how well the person will work out on that team?

Re:Girls Who Code by philwelch on Monday December 30, 2013 @12:13PM (#6985510)
People who experience personality conflicts with each other can be civil to each other and interact in a professional capacity. Not being able to do that might be a problem, but we're all adults here.
Re:Girls Who Code by gordaco on Sunday December 29, 2013 @07:56PM (#6982439)
Maybe I'm being too dramatic, but I see the concept of "cultural fit" as highly toxic and counterproductive, and that's without taking into account that (IMHO) it reflects some kind of fear and insecurity on those who promote it, who seem to be wary of being surrounded by different kinds of people. The effect on women who could potentially get into coding is just one of the multiple effects (although maybe the most prominent).
Re:Girls Who Code by Nursie on Sunday December 29, 2013 @03:38PM (#6981240)
I used to work at Big Blue and got very used to the 'no discrimination' thing they had. So much so that now I'm outside it and working for smaller companies I've really noticed how horrible some of the attitudes towards women are in some of the smaller workplaces here (UK). It's really sickening and while a lot of it is from the older generation (50+) the younger folks aren't blameless either.
Re:Girls Who Code by revelation on Sunday December 29, 2013 @03:17PM (#6981115)
I think we need to be very clear that the programming jobs of that era are not todays programing jobs. It was 1980, general society wasn't very progressive, why would computer programming be the magic beacon of equality? And, of course, it wasn't, it was considered menial work fit for females.
Re:Girls Who Code by judk on Sunday December 29, 2013 @04:53PM (#6981584)
I have heard that argument for jobs, but what about Bachelors Degree majors?

To me, the bigger difference is that there must be 10-100x more CS majors per year now than in 1985. CS was mostly applied math then, and math majors have long been extremely majority male.

Re:Girls Who Code by macNchz on Monday December 30, 2013 @11:07AM (#6985110)
>To me, the bigger difference is that there must be 10-100x more CS majors per year now than in 1985. CS was mostly applied math then, and math majors have long been extremely majority male.

Actually, according to the second chart on this page(1), there are almost exactly the same number of CS bachelors degrees granted today as there were in 1985 (~41k). Also, the percentage of women in 1985 was double that of today.

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

Re:Girls Who Code by lmm on Monday December 30, 2013 @06:37AM (#6984173)
Doesn't the same argument apply? Mathematics was not a high-status degree in the '50s, and it was only when it became more respected (and lucrative) that feminists started to have a problem with the gender imbalance.
Re:Girls Who Code by pygy_ on Sunday December 29, 2013 @04:04PM (#6981385)
Re:Girls Who Code by kro0ub on Sunday December 29, 2013 @10:28PM (#6982866)
I particularly appreciated your classification of McDonald's as a startup.
Re:Girls Who Code by moron4hire on Sunday December 29, 2013 @03:44PM (#6981284)
Glad to see someone else bringing up the "cultural fit" bullshit.
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)