My favorite interview was at digg.com. A four hour interview was going great. My dream job. I knew their tech solid. Then the last guy - walked in [ianeure]. He asked: "What is a having statement in sql". I leaped in - rambled on and on how you can filter aggregated sets. His response: "I don't think you know how they work." I sat there confused and concerned. He explained you don't need a group by with a having stat…
The software industry's greatest sin: hiring
581–590 of 590 posts
Re: The software industry's greatest sin: hiring
#582My favorite interview was at digg.com. A four hour interview was going great. My dream job. I knew their tech solid. Then the last guy - walked in [ianeure]. He asked: "What is a having statement in sql". I leaped in - rambled on and on how you can filter aggregated sets. His response: "I don't think you know how they work." I sat there confused and concerned. He explained you don't need a group by with a having stat…
I'm sorry you didn't have a good interview at Digg. My goal, then and now, is that even people who don't get an offer should leave feeling okay about the process. I clearly didn't live up to that with you, and I apologize for it. We never made a no-hire decision based on one answer, and nobody ended an interview after one question, unless there was some sort of emergency. Site outage, fire alarm, that sort of thing.…
Re: The software industry's greatest sin: hiring
#583Earlier quoted context omitted.
If you assume roughly even distributions of talent across gender Given the differences in the genders of who chooses to study the relevant qualifications, that's obviously a false assumption. The amount of just unsourced vitriol of your comment is unapproachable My comments are phrased in a level, factual manner. They're mostly retellings of things seen or experienced first hand, thus I am myself the source. But if y…
My bad for the previously missing source that's on me. Ive expanded on the thought below with references. (and despite calling me out you still can't find a single source for your claims (short of a vague, go read a document I clearly haven't read for me, which is just, beautiful)) Edited previous comment for the missing source, that's my bad. (and despite calling me out you still can't find a single source for your…
This isn't even a grammatical sentence, but you appear to be suggesting that being told what to read isn't providing a source, which is nonsensical.
Go read: https://www.documentcloud.org/documents/4391847-18-CIV-00442...
To repeat - for most of what I've written I'm the source. Make of it what you want. What I've seen is consistent with similar claims made by others, many times in many contexts. The tech industry discriminates against men systematically, and it's because of the distorted ideological beliefs of people like you!
That puts the ceiling closer to between 30 and 40 percent[0, for a representative top tier school
GA Tech isn't representative. Even your own linked document says that: "Georgia Tech also awards more engineering degrees to women than any other U.S. institution"
GA Tech is famous for having a much higher proportion of women on its courses than normal. I guess someone told you it's a success story and now it's your go-to example.
They "achieved" this by systematically discriminating against men, which has led to a Title IX complaint against them for no less than ten different programs:
https://www.aei.org/carpe-diem/title-ix-updates-ocr-opens-in...
They routinely ban men from all sorts of events so if you believe this is an example of an unbiased selection process you're making my case for me. Men are systematically discriminated against and women never are: the disparate outcomes reflect fundamental differences and NOT some sort of non-existent bias against women.
Let's even abandon, for the sake of argument, any desire to see ratios in engineering even approach demographic ratios
You act like it's an absurd position to "abandon", but it's an absurd position to have in the first place. Let's not do for-the-sake-of-argument, let's deal with reality. Nearly all jobs have distributions different to base demography.
Here's a chart you should look at: https://www.bostonglobe.com/metro/2017/03/06/chart-the-perce...
You're picking on engineering here, but why not pick on:
1. Kindergarten teachers, 97.% female
2. Dental hygienists, 97.1% female
3. Nurses, 90% female
4. Phlebotomists, 86.% female
5. Insurance claims processors, 85% female
All these jobs are less representative of the population than programming, which at merely 80% male is significantly less far from 50/50 than a huge number of teaching and medical related roles.
If you scroll the list you'll see that most professions aren't even close to 50/50.
“Thing exists” does not imply “thing normal” or “thing ideal”[3]. That’s a common logical fallacy used to justify traditionalism in all forms
Actually this kind of thinking is itself a logical fallacy. You're starting from a base point of assuming you can understand the reasons for absolutely every fact about the world, which clearly isn't the case. To believe you can decide what is ideal in any area of human existence requires a vastly over-exaggerated sense of one's intellect.
What you call traditionalism is really just a starting assumption that when studying complex evolved systems there are reasons for its current state that you may not understand. This is a perfectly rational assumption and made all the time in e.g. medicine. It's an assumption of incomplete information and inaccurate methods, that can lead to creating new problems instead of solving them. It's what led to "first, do no harm" as a medical concept.
When we look at technology it’s especially strange because there is no clear mechanism (outside of social bias) that might explain why we’d see the ratios present.
This is the root of the problem - that belief is pure ideology. The obvious explanation is that women find technology less interesting than men because they're women and women are different to men, in all sorts of complex ways. This statement is like saying "there's no clear mechanism for why almost everyone who works with children is a woman". Of course there's a clear mechanism for it: they're women, they have babies, they evolved to want to care for children as a result and thus women very often enjoy children's company more than men do. The idea that anything other than the base 50/50 case must be bias ignores not only vast amounts of basic evolutionary theory but also common sense.
In the end I'm arguing with you because it's people like you who ultimately argue for and implement anti-male discrimination, on the belief that you're on some grand moral quest to eliminate discrimination against women. But like Animal Farm, the evil you think you're fighting is in fact yourself - the only gender based discrimination I've ever seen in my entire career was done by feminists.
Re: The software industry's greatest sin: hiring
#584This article was painful for me to read, mostly because of how accurately it reflected my experience with job searching. I'm not the worlds most experienced dev who's shipped multiple products, but for a relatively inexperienced (2y professional, 5y total), I feel I am overlooked for positions I would excel in because I am just plain bad at technical interviews. I have a fairly impressive github, a creative cv and re…
Sounds like you know exactly what your problem is. Technical interviewing is just like normal problem solving, just you have to narrate your thoughts as if the interviewer's inside your head with you. Get some sample problems that match what you're seeing in your onsites, roleplay having an interviewer there with you, and practice them while recording yourself. Best is if you can have a real human. If you're passiona…
Under normal circumstances, I sit and problem solve, thinking only of the issue at hand, branching out and following leads and so on.
Under interview circumstances, I instead try to anticipate what the person scrutinising me wants to see, and try to like, game an ungameable situation, which blocks my natural problem solving thinking.
I have noticed that when I'm in a position of subordination, I do worse creatively. This isn't to say I can't work as employee, but rather in specific situations, such as "person knows x and is just watching me try to do x", I enter this reactive thought mode.
Conversely, when I am in a superordinate position, I find myself much more creative than my baseline, thinking clearly and well.
I don't know how to handle this for interviews.
Re: The software industry's greatest sin: hiring
#585Earlier quoted context omitted.
> Absent any other evidence though, the simplest explanation is that domain specific knowledge is likely useful. Disagree; surely the null hypothesis for any given training programme is that it has no effect. > The point is that the more unusual someone's background is, the more likely you are to remember it. Particularly if there is some confirmation bias involved. There isn't anything unusual about professional pro…
>Disagree; surely the null hypothesis for any given training programme is that it has no effect. That's not what's under test here though. It's training program A that includes domain specific knowledge or training program B that does not. >There isn't anything unusual about professional programmers having a degree in maths or physics rather than CS. At least in my experience it was pretty close to an equal split. Lo…
I suspect SO surveys are heavily biased towards younger developers, but even taking those 2019 numbers at face value: about 20% of professional developers have no degree, and of those with degrees it's about 75% CS/information systems/sysadmin/webdev, 17% maths/physics/engineering, and 8% other. So a typical 15-developer team would be 9 with CS degrees, 3 with no degree, 1 with an engineering degree, 1 with maths/science and 1 other. The non-CS folk are not exactly rare unicorns.
Re: The software industry's greatest sin: hiring
#586Earlier quoted context omitted.
>Disagree; surely the null hypothesis for any given training programme is that it has no effect. That's not what's under test here though. It's training program A that includes domain specific knowledge or training program B that does not. >There isn't anything unusual about professional programmers having a degree in maths or physics rather than CS. At least in my experience it was pretty close to an equal split. Lo…
I'm not talking about a maths or physics degree specifically. I'm talking about having a CS degree or not. The stack overflow survey seems to have shifted towards CS recently; the 2015 results (earliest I could find) imply 52% of professional developers had CS degrees at that point, which was about halfway through my career so far, so 50:50 for people I've worked with sounds about right. I suspect SO surveys are heav…
Well then why did you say this:
>There isn't anything unusual about professional programmers having a degree in maths or physics rather than CS. At least in my experience it was pretty close to an equal split.
You said explicitly math and physics degrees vs CS degrees. And you previously said the best programmers tended to have math, or physics degrees or something similar.
This isn't me being pedantic, it was the entire context of the discussion.
The point is that you are prone to confirmation bias as evidenced by your belief that it's close to an equal split. Your mental model is overrepresenting people with physics and math degrees likely because it confirms your belief that they are better programmers.
>So a typical 15-developer team would be 9 with CS degrees, 3 with no degree, 1 with an engineering degree, 1 with maths/science and 1 other. The non-CS folk are not exactly rare unicorns.
That's not the point, it's that you are more likely to remember the background of the 1 person on a team who has a Math degree because she is relatively rare compared to all of the people with CS degrees. This is a well known and well documented phenomenon. And it's one of the primary reasons that anecdotal evidence, even a large amount of anecdotal evidence is so often wrong.
Re: The software industry's greatest sin: hiring
#587Earlier quoted context omitted.
I'm not talking about a maths or physics degree specifically. I'm talking about having a CS degree or not. The stack overflow survey seems to have shifted towards CS recently; the 2015 results (earliest I could find) imply 52% of professional developers had CS degrees at that point, which was about halfway through my career so far, so 50:50 for people I've worked with sounds about right. I suspect SO surveys are heav…
>I'm not talking about a maths or physics degree specifically. I'm talking about having a CS degree or not. Well then why did you say this: >There isn't anything unusual about professional programmers having a degree in maths or physics rather than CS. At least in my experience it was pretty close to an equal split. You said explicitly math and physics degrees vs CS degrees. And you previously said the best programme…
I was giving those as examples of degrees that are normal and don't stand out. We don't think there's anything particularly odd about a programmer with a maths or physics degree. That's all I was saying.
> you previously said the best programmers tended to have math, or physics degrees or something similar.
A category which would include engineering, at which point we're at 20-25% of professional programmers with degrees by your numbers (which I still think are significantly biased).
> The point is that you are prone to confirmation bias as evidenced by your belief that it's close to an equal split. Your mental model is overrepresenting people with physics and math degrees likely because it confirms your belief that they are better programmers.
My mental model is that it's an equal split between CS degrees and not, and per your own sources that's accurate. You're fixating on a couple of specific examples of non-CS degrees that I mentioned when that's completely beside the point.
Re: The software industry's greatest sin: hiring
#588Earlier quoted context omitted.
>I'm not talking about a maths or physics degree specifically. I'm talking about having a CS degree or not. Well then why did you say this: >There isn't anything unusual about professional programmers having a degree in maths or physics rather than CS. At least in my experience it was pretty close to an equal split. You said explicitly math and physics degrees vs CS degrees. And you previously said the best programme…
> You said explicitly math and physics degrees vs CS degrees. I was giving those as examples of degrees that are normal and don't stand out. We don't think there's anything particularly odd about a programmer with a maths or physics degree. That's all I was saying. > you previously said the best programmers tended to have math, or physics degrees or something similar. A category which would include engineering, at wh…
>The best programmers I've worked with have mostly not had CS degrees (tended to have degrees in maths, physics, or that sort of area).
That's the entire context of the discussion. The assertion that CS majors have worse outcomes (with respect to programming ability) than math, physics or similar majors.
>A category which would include engineering, at which point we're at 20-25% of professional programmers with degrees by your numbers (which I still think are significantly biased).
If you are including math, all natural sciences, and all other engineering degrees you get 17%, not 20-25%.
>My mental model is that it's an equal split between CS degrees and not, and per your own sources that's accurate. You're fixating on a couple of specific examples of non-CS degrees that I mentioned when that's completely beside the point.
There is no other logical way to parse this statement
>There isn't anything unusual about professional programmers having a degree in maths or physics rather than CS. At least in my experience it was pretty close to an equal split.
than that you were talking specifically about math and physics.
I get it, you don't like that there are numbers that contradict you, so you are grasping at straws trying to find alternate interpretations to reconcile your statement with the numbers. You obviously don't like being wrong. I don't either, that's fine, but no one other than us is reading this far down. There's not point denying you farted when there's only 2 of you in an elevator.
Re: The software industry's greatest sin: hiring
#589Re: The software industry's greatest sin: hiring
#590Earlier quoted context omitted.
As an employee of Google who is involved in hiring let me tell you the process is extremely rigorous and we work very hard to make it bias free. I am not an unbiased individual myself but when it comes to hiring, I work extra hard to ensure fairness regardless of other person's characteristics.
And as a former Googler who did hundreds of interviews there, let me tell you you're wrong. It wasn't bias free even years ago, and Google has gone much more hard-core SJW since then. It's still much better than at most companies, and the article we're discussing is so wrong about the way executives are hired. But Google isn't some paragon of freedom from bias, far from it. Ignore yourself. The system surrounding you…
Not my claim that Google is bias free. I am not denying what you have claimed, it is just that I have not come across such incidents and if you are a qualified person it is extremely unlikely that I will not judge you performance properly because of your gender, race or ethnicity.
There is no doubt that Google has gone lala SJW route in last few years but then many of us put conscious efforts in fixing those problems.