News for hackers. Stuff that matters.
Re:Signaling in tech is some fucked up shit (2016) by iwangulenko on Sunday July 29, 2018 @05:39PM (#17640414)
As someone running a technical recruitment agency, I can assure you that it is true that someone having built stuff in Clojure is more likely to be considered as a good engineer than someone who did JQuery all the time.

Recruiters use an intuitive approach to conditional probability. Given only the info alone (if someone did JQuery or Clojure) exposes you to two bell curves, with the X-axis being "programming ability". The first bell curve that has all JQuery people is more on "the left" and the one having all Clojurians is more on the right. The Clojure bell curve has shitty engineers and some really good people are part of the JQuery one.

Prejudice is sort of rational. If a recruiter looks at one datapoint, it's unlikely that it is at the tails of the bell curve, so the Clojurian applicant will get more attention. If you are treated unfairly because of the group you "belong to", I am sorry - but this is reality.

Re:Signaling in tech is some fucked up shit (2016) by braythwayt on Sunday July 29, 2018 @07:08PM (#17640887)
I have decades of experience hiring people, and what I find is this:

If I randomly select a programmer from all the programmers who write Clojure, working or not, interviewing or not, they are likely to be a “better” programmer than if I randomly select a programmer from all the programmers who write JavaScript, working or not, interviewing or not.

But of course, that’s not what happens when I interview. I meet one person in the morning with three years experience working on projects of types A, B, and C. In the afternoon I meet another with four years of experience working on projects of types B, C, and D.

If one has Clojure and the other JavaScript, I’m much more likely to be delighted to discuss Clojure than JavaScript, but as far as HIRE/NO HIRE is concened, the thing that matters to me are projects Of type A, B, C, or D, and the candidate’s role/contribution.

If the JavaScript programmer’s experience is solid, I do not want a recruiter in-house or otherwise trying to save me an interview and filtering them out.

The bottom line is, there are like 100x as many JS folks as CJ folks. So let’s say there are 100 great CJ people out of 1,000 CJ people. 10% ham!

But that means there are 100,000 JS people. If even 1% of them are great, that means that there are 1,000 great JS people out there, and I do not want to pass on meeting any of them just because there are also 99,000 not-so-great JS people out there.

In my imaginary distribution, a random CJ person is 10x more likely to be good. But there are 10x as many good JS people as CJ people, and my experience is that THEIR experience is a far better signal than their programming language.

—-

p.s. I am competing with people who only want to hire programmers with shiny signals like ClojureScript or the ability to quote “JavaScript Allongé.” Good! Let them ignore the 1,000 good JS people, easier for me to interview them and make a successful offer.

Now that I think about it, please ignore what I just said. Only interview people who build systems out of Lisp, Prolog, and Maleboge.

Re:Signaling in tech is some fucked up shit (2016) by karmakaze on Sunday July 29, 2018 @07:22PM (#17640941)
We're currently interviewing for positions which I haven't done in a while. There are many more developers and even more completion for them. The number of resumes read and interviews conducted for a Sr. position has gone up. I have found selecting candidates with more diverse exposure/interests greatly increases the s/n ratio and gladly do this knowing I'm missing some. It's just more effective in terms of time taken out of team capacity to do interviews.
Re:Signaling in tech is some fucked up shit (2016) by GijsjanB on Sunday July 29, 2018 @07:37PM (#17641011)
I have 0 years hiring people, my experience is this. The language(s) you write code in don't mean a thing. It's the ecosystem. I'm a JS programmer, but that is not why you should hire me, it's my experience with the DOM, HTTP, indexeddb, File API, documentFragment, Fetch API, TreeWalker, NPM, WebGL, interactive SVG, the pros and cons of React, when to use Redux, Basic login, NGINX, Docker, etc, etc, etc. My point is this: knowledge of Closure(Script) is a great tool in any programmers tool belt, but it is definitely not the most important one for a solid frontend engineer.
Re:Signaling in tech is some fucked up shit (2016) by louthy on Sunday July 29, 2018 @08:23PM (#17641228)
Knowledge of APIs is not a good indicator of ability in my experience (I have many years of hiring people). So, the 'ecosystem' isn't particularly interesting and neither are the devs that just put endless lists of acronyms on their CVs. It's much more useful to listen to a dev tell you how they solved various problems, dig into their CS knowledge, see what they like working on in their spare time (code or not code related).
Re:Signaling in tech is some fucked up shit (2016) by denkmoon on Sunday July 29, 2018 @09:30PM (#17641454)
When I see an interviewee list out a bunch of things they have "experience" with like that, I assume they actually mean "I used this once".
Re:Signaling in tech is some fucked up shit (2016) by Hydraulix989 on Sunday July 29, 2018 @10:37PM (#17641665)
It's hard to avoid touching the DOM, HTTP, NPM, React, NGINX, Docker, etc. on a daily basis if you're doing any kind of serious work; it's not just some disjoint list of obscure buzzwords.
Re:Signaling in tech is some fucked up shit (2016) by braythwayt on Monday July 30, 2018 @11:20AM (#17645015)
Yes, compare and contrast the above to my own partial list of technologies from 1977 to 1997...

“Nova 1220 BASIC, Acius 4th Dimension, Hypercard, MetroWerks CodeWarrior, Lightspeed C, Turbo Pascal, MP/M, DigiTalk Smalltalk/V, J2EE, ...”

What does any of that have to do with each other.

Re:Signaling in tech is some fucked up shit (2016) by scroot on Monday July 30, 2018 @01:05PM (#17646004)
There's one thing: Hypercard and DigiTalk represent directions personal computing should have gone, but didn't (although that's not relevant to the thread topic)
Re:Signaling in tech is some fucked up shit (2016) by denkmoon on Monday July 30, 2018 @11:22PM (#17650307)
It's not so much that someone has touched <acronym soup> rather the kind of people that think just listing all that out is useful, are typically not the developers I want.
Re:Signaling in tech is some fucked up shit (2016) by msds on Sunday July 29, 2018 @09:08PM (#17641388)
You just named a lot of things. Why should I hire you?
Re:Signaling in tech is some fucked up shit (2016) by GijsjanB on Monday July 30, 2018 @01:56AM (#17642362)
Ok, the list is distracting. I mean, experience with web dev's ecosystem is more important than the languages you can write code in. Of course a list on it's own is useless, it should be supported with actual projects (hopefully some in production).
Re:Signaling in tech is some fucked up shit (2016) by ender7 on Sunday July 29, 2018 @06:25PM (#17640665)
It's true that, based on my interviewing experience, candidates with only a jQuery background are unlikely to have the skills to cut it developing large-scale software at a large-scale company, which is what I am hiring for. At the moment I interview mostly front-end candidates, and it takes a lot of sifting to find qualified hires.

However, the implicit companion assumption that a resume with lots of clojure experience will have those skills is not something I've seen any evidence for. Many Clojure-focused candidates are unproductively dogmatic and are at risk of wasting everyone's time by trying to rearchitect our codebase because it doesn't meet their particular taste. In general, if a candidate is an adherent to a niche programming language they need to be able to explain to me when its use would be appropriate and inappropriate. If their answer is "this language and/or dogma is always better" then you're adorable but you need some more experience before I'm going to hire you.

It's also important to point out that, while my core requirements are the same for both jQuery and Clojurey candidates (ability to function in a large, complex codebase & ability to manage your own code's complexity), the specific skillsets are very different. Most clojure enthusiasts are actively bad front-end engineers. Which is fine! But many positions require engineers to at least be able to dabble in UI work, and if I get the sense that you would find it beneath you to do so, its probably going to mean better luck somewhere else unless I have a very specific position to fill.

Re:Signaling in tech is some fucked up shit (2016) by s3nnyy on Sunday July 29, 2018 @06:30PM (#17640701)
Oh yes. Based on my experience hiring on behalf of different firms, arrogance among engineers correlates with the degree of mathy-ness of a stack.
Re:Signaling in tech is some fucked up shit (2016) by bm1362 on Monday July 30, 2018 @12:52AM (#17642146)
This is my experience hiring Clojure engineers in a small startup- things became dogmatic and opinionated at a time when we were existentially challenged with building a product.
Re:Signaling in tech is some fucked up shit (2016) by raiflip on Sunday July 29, 2018 @05:58PM (#17640510)
That is definitely a good strategy for a recruiter. However the context of the author's experience seems to be how the author's coworkers treats them. If I'm working with someone and I get to see their code, or I can take a look if I'm curious, IMO it becomes a vice to use Bayesian probability when you can look at the person's actual code and judge their skill. A different way to put it is Bayesian probability is good in a situation of uncertainty, but if you are not in a situation of uncertainty it just becomes lazy/ prejudicial.
Re:Signaling in tech is some fucked up shit (2016) by throwawaymath on Sunday July 29, 2018 @05:44PM (#17640436)
> As someone running a technical recruitment agency, I can assure you that - statistically speaking - it is true that someone having built stuff in Clojure is more likely to be a good engineer than someone who did JQuery all the time.

Would you care to share those statistics? While we're at it let's also be sure to define "good engineer."

Re:Signaling in tech is some fucked up shit (2016) by s3nnyy on Sunday July 29, 2018 @05:48PM (#17640454)
Experience looking at thousands of CVs and talking to people who are behind the CVs.
Re:Signaling in tech is some fucked up shit (2016) by throwawaymath on Sunday July 29, 2018 @05:51PM (#17640478)
That's not a statistic, nor is it quantifiable. I'm not taking issue with your experience, I'm taking issue with the fact that you've implied your claim has quantitative rigor to it, because I'm extremely skeptical that's the case.

For what it's worth, I'm challenging you as someone who is neither a JavaScript developer nor a Clojure developer. I'm of the opinion that biases like the one the author laments are perpetuated (in part) by this leaky arguments from "statistics" that never appear.

Re:Signaling in tech is some fucked up shit (2016) by scarejunba on Sunday July 29, 2018 @06:34PM (#17640721)
Don't get hung up on the language. People sometimes say "statistically speaking" to mean "Based on my experience over a large number of tests". It doesn't mean "I applied a test of statistical significance to arrive at my conclusion".

You're then meant to combine their stated experience with their stated credentials and your assessment of their trustworthiness to arrive at some conclusion.

This imprecision may annoy you but it is a common way of speaking English so it's probably not in your interest to fight over the choice of wording.

Re:Signaling in tech is some fucked up shit (2016) by throwawaymath on Sunday July 29, 2018 @06:57PM (#17640826)
Sure, I understand what you're saying. But I'll continue to challenge the use of language like that. In my opinion, saying something is true "statistically speaking" is more grievous than saying something like, "I'm 99% sure." Both are artifacts of the English language, but I think the former carries much more quantification behind it, implicitly speaking. In that sense it's not just about informal use of language.

This is because saying something is true "statistically" is a claim made in both scientific and casual contexts. It's mentally taxing to figure out which context is in play - someone could have come into this thread with actual statistics and said the same phrase, verbatim. Therefore (as I see it), it's realistically plausible that someone could read the original comment and come away believing recruiters have done actual statistical analysis a la TripleByte to arrive at their conclusion.

Re:Signaling in tech is some fucked up shit (2016) by s3nnyy on Sunday July 29, 2018 @07:07PM (#17640882)
I hear you. I removed the wording "statistically speaking" from the initial comment.
Re:Signaling in tech is some fucked up shit (2016) by freshhawk on Sunday July 29, 2018 @10:35PM (#17641655)
In english, "statistically speaking" can mean you are making a claim about the odds of something rather than a 1:1 correspondence. It is extremely common and absolutely correct.

For example I have not run a study but I am very confident that, statistically speaking, tall people are better at basketball than short people. I am saying that I have an opinion that if you were to try and choose good basketball players, biasing yourself towards the tall people will increase your odds of making a good choice. I use the phrase "statistically speaking" to make it clear I am not saying "All tall people are better at basketball than short people".

In a lot of contexts you will drop the phrase completely because you are talking to other smart people and they will know that the context of your statement is in the realm of populations and odds, but online there are a lot of pedants with poor communication skills so you have be extra clear.

Re:Signaling in tech is some fucked up shit (2016) by throwawaymath on Sunday July 29, 2018 @11:17PM (#17641781)
If you believe this is about pedantry and the literal meaning of words, you’ve missed my point. However, you’re speaking to it: the commenter used the phrase “statistically speaking” to indicate their confidence in their assertion. I’m taking issue with the fact that they used the phrase - which, as you say, is strong enough to describe the way taller people are better at basketball - to generalize that Clojure developers are more likely to be qualified than JavaScript developers.

Idiomatically, any way you use the phrase implies great confidence in the corresponding claim. But I have not seen any substantial explanation of why this effect makes sense, which makes me extremely suspicious that the effect exists at all. I don’t particularly care about whether they’ve conducted a peer reviewed study. I care about whether or not their heuristic is backed by anything empirical. “I’ve noticed this...” doesn’t cut it, no matter how fast and loose you want to play with the literal meaning of the word in context.

Re:Signaling in tech is some fucked up shit (2016) by freshhawk on Monday July 30, 2018 @12:09PM (#17645495)
It doesn't imply great confidence, it is literally saying a different thing. You seem to think it means the same thing as "scientifically speaking" or "I have evidence that". It very often means only "related to statistics". That's it. No epistemological claims needed.

"I'm so going to win the lottery"

"On average ... no you aren't" / "Statistically speaking ... no you aren't" / "If you work out the odds ... no you aren't" / etc.

If I ask you a question about some gambling game, you are going to think about it in a statistical way. I mean you will think in terms of populations and samples and odds, not that you will go perform experiments and then do a statistical analysis of that evidence in order to come to a scientific conclusion.

Re:Signaling in tech is some fucked up shit (2016) by jholman on Monday July 30, 2018 @02:47PM (#17646912)
I think you're mistaken.

I, like you, am riled up by people using puff words to inflate the apparent credibility of claims, often claims that have little or no basis for actual credibility.

But I think that "statistically speaking", as it is used by nearly all English speakers, means "speaking about these groups in aggregate", not "speaking as a statistician". It doesn't even mean something about an empirical basis, it means talking about groups. I agree pretty much entirely with freshhawk's analysis.

Now, aside from _word choice_, your skepticism about whether the original poster has any empirical basis at all for their claim... well, fair enough.

Re:Signaling in tech is some fucked up shit (2016) by parrellel on Sunday July 29, 2018 @05:45PM (#17640440)
He just said it was holistic.
Re:Signaling in tech is some fucked up shit (2016) by throwawaymath on Sunday July 29, 2018 @05:50PM (#17640469)
The commenter said "statistically speaking" to justify part of their point. I am directly challenging their assertion and requesting evidence that they have 1) actually quantified something in more than a hand wavey manner, and 2) found the (falsifiable) conclusion they stated, based on that analysis.

I'm deeply skeptical. People like to throw around percentages and references to statistics to justify their biases, but I don't think the commenter has done nearly enough to motivate the conclusion that the modal Clojure developer is more likely to be a "good engineer" than the modal JavaScript developer.

Re:Signaling in tech is some fucked up shit (2016) by sonnyblarney on Sunday July 29, 2018 @06:05PM (#17640549)
Next time you have a blocked toilet, and the plumber says it's a problem with 'ABC' why don't you just tell him that's not quantifiable! and then tell him you think it's 'XYZ' that's the problem.

If someone who interviews thousands of people and finds a correlation between those who have some clojure experience and quality, I believe him.

For the simple reason that most programmers don't try very hard and anyone taking the time to even learn a rarely used language is demonstrating a positive quality that most don't.

Re:Signaling in tech is some fucked up shit (2016) by throwawaymath on Sunday July 29, 2018 @06:50PM (#17640800)
If the plumber can explain to me in coherent reasoning why the problem is likely with 'ABC', I'm not going to challenge it. Especially if they don't handwave about statistics they almost assuredly don't have and I have no domain experience in plumbing. That analogy doesn't work.

I stand by my point: using words like "statistically" and "correlation" perpetuate biases which may not have a rational basis. In this entire thread no one has explained why Clojure programmers are more likely to be "good" than JavaScript programmers (nor has "good" been defined!). I could just as plausibly state that someone tried to learn Clojure because they perceive it to be a buzzword, just as JavaScript programmers are often accused of playing buzzword bingo with web development frameworks.

Empirically speaking, we haven't ended up anywhere. No matter how sure you are of this phenomenon, unless you try to make its observation more robust, it will continue to be a microcosm of the tech hiring industry. Heuristics often belie subtle biases that do not actually have a foundation in truth.

Re:Signaling in tech is some fucked up shit (2016) by gaius on Tuesday July 31, 2018 @03:42AM (#17651282)
most programmers don't try very hard and anyone taking the time to even learn a rarely used language is demonstrating a positive quality that most don't.

Once known as the Python Paradox http://www.paulgraham.com/pypar.html

Nowadays I suppose it would be the Clojure Conundrum or the Haskell Happenstance

Re:Signaling in tech is some fucked up shit (2016) by k__ on Sunday July 29, 2018 @06:38PM (#17640740)
I never talked to a recruiter with any technical expertise in my whole 12 year career.
Re:Signaling in tech is some fucked up shit (2016) by oblio on Sunday July 29, 2018 @06:41PM (#17640759)
Re:Signaling in tech is some fucked up shit (2016) by lifeisstillgood on Sunday July 29, 2018 @06:45PM (#17640774)
Funny, but presumably just selecting for recruiters with deep knowledge of pokemon, not programming languages.
Re:Signaling in tech is some fucked up shit (2016) by minikomi on Sunday July 29, 2018 @10:43PM (#17641693)
And you're assuming pokemon trainer abilities aren't congruous with tech recruiting.
Re:Signaling in tech is some fucked up shit (2016) by 1123581321 on Sunday July 29, 2018 @08:40PM (#17641291)
Which is krebase? Google seems to only return references to this image.
Re:Signaling in tech is some fucked up shit (2016) by oblio on Tuesday July 31, 2018 @05:59AM (#17651850)
Beats me, not my image :)
Re:Signaling in tech is some fucked up shit (2016) by k__ on Sunday July 29, 2018 @07:06PM (#17640880)
It's really sad, because I get called by 2 of them a week :/

Their websites sound like they are the pinnacle of the industry, but on phone/email they sound like a bunch of HS dropouts :(

Re:Signaling in tech is some fucked up shit (2016) by mlthoughts2018 on Sunday July 29, 2018 @09:41PM (#17641497)
I think it’s pure hubris to say that anyone can distinguish overall skill at a statistically significant level between these different populations.

Heck, I’d even say if you only look at the population of engineers who you have directly observed doing a good job on some interview trivia or code test, you still cannot reliably conclude that draws from that population are statistically significantly more likely to be acceptably good at a job once hired than draws from a different population.

People and processes capable of detecting skilled engineers are extremely rare. Skilled engineers are also somewhat rare.

What we set up as tech hiring processes are mostly just crap-shoot just-so stories we tell ourselves, mixed with a ton of hubris.

Re:Signaling in tech is some fucked up shit (2016) by panic on Sunday July 29, 2018 @06:01PM (#17640528)
Presumably people are paying you to find good engineers, not just people who match particular profiles. If "rational prejudice" doesn't always find the good engineers, why justify it like this? Wouldn't it be better to take this as evidence that your approach could use improvement?
Re:Signaling in tech is some fucked up shit (2016) by curun1r on Sunday July 29, 2018 @06:42PM (#17640768)
> people are paying you to find good engineers

No, they're paying them to find engineers that will pass the interview process. It's a subtle, but important distinction since prejudices that exist among engineers will naturally develop in recruiters. It's the recruiting equivalent of teaching to the test.

And like it or not, the kind of signaling the article describes is real. When an engineer says they can write clojure, it indicates a curiosity that ability to program JavaScript does not. Almost no one is forced to learn Clojure because of some job, project or even job prospects. It means you likely cared enough to devote your own time to learning for the sake of learning. And a lot of engineers look at this kind of thing as important and screen for it in interviews.

A recruiter operating any differently would be like a machine learning algorithm that ignores its training data.

Re:Signaling in tech is some fucked up shit (2016) by gaius on Tuesday July 31, 2018 @03:56AM (#17651345)
It means you likely cared enough to devote your own time to learning for the sake of learning. And a lot of engineers look at this kind of thing as important and screen for it in interviews.

The curious thing is, I think the number who regard it as important is likely far higher than the number who actually do it. Which is understandable; once you reach a level of seniority you also have many other demands on your time and may not be able to be a hobbyist anymore on top of day job, family commitments and so on. So maybe once you learnt every new language but now you don’t have the opportunity, or you have decided to “go deep” in just a few, established languages. So the power of the signal is highly variable depending both on where the interviewer and interviewee are in their lives.

Also, knowing JS in the late-90s did indicate a curious and ambitious developer. It only went mainstream later...

Re:Signaling in tech is some fucked up shit (2016) by darawk on Sunday July 29, 2018 @06:15PM (#17640612)
No. You have limited resources to sift through people. Heuristics like this are an efficient way to reduce your search space. That is sort of the whole point of statistics.
Re:Signaling in tech is some fucked up shit (2016) by machiavelli1024 on Sunday July 29, 2018 @05:46PM (#17640444)
Yep. Funny that HackerNews seem to be unable to wrap their head around the fact that prejudice is just applied Bayesian statistics.
Re:Signaling in tech is some fucked up shit (2016) by dang on Sunday July 29, 2018 @06:57PM (#17640828)
Please don't take HN threads on generic ideological tangents.

https://news.ycombinator.com/newsguidelines.html

Re:Signaling in tech is some fucked up shit (2016) by MusaTheRedGuard on Sunday July 29, 2018 @05:51PM (#17640475)
I'm gonna say prejudice is actually not applied Bayesian statistics
Re:Signaling in tech is some fucked up shit (2016) by bastijn on Sunday July 29, 2018 @06:02PM (#17640537)
and you would be right. Say I have a broken phone which is an Android. A prejudice would be that androids are likely to break. Mathematically we could represent as

  P(broken|android) =~ P(android|broken)
We see from Bayes rule that this is false, since

  P(android) >> P(broken)
Re:Signaling in tech is some fucked up shit (2016) by braythwayt on Sunday July 29, 2018 @06:51PM (#17640804)
Even worse, what actually happens with prejudice is that if I think that Androids are shitty phones, when I see a broken Android, I add it to my collection of “Shitty Android” data points.

But when my iPhone breaks, I take it into Apple for service and add it to my collection of “Apple gives great service” data points.

Saying that prejudice is just applied statistics completely mischaracterizes prejudice.

Re:Signaling in tech is some fucked up shit (2016) by mrexroad on Sunday July 29, 2018 @06:07PM (#17640568)
I’d argue that prejudice and bias applies most all statistics, but most often we just don’t notice or care. E.g. The biases inherent to specific domain, of those who captured the data, those who selected the data, selection of statistical techniques, real-world outcomes reinforced by usage of these statistics, etc.
[dead]
Re:Signaling in tech is some fucked up shit (2016) by dang on Sunday July 29, 2018 @10:39PM (#17641677)
Please don't take HN threads on generic flamewar tangents. Especially not this, for the god knows how manyth time.
Re:Signaling in tech is some fucked up shit (2016) by wellpast on Sunday July 29, 2018 @06:44PM (#17640770)
Your question assumes that the programming talent bell curve for men and women are different, which I wouldn’t expect to be the case.
Re:Signaling in tech is some fucked up shit (2016) by bsder on Sunday July 29, 2018 @07:44PM (#17641057)
Almost nothing in nature matches that statement.

The "Bell Curve" for females of a species generally has a significantly narrower standard deviation for practically any genetically driven characteristic.

The problem is that none of this applies to an individual.

Re:Signaling in tech is some fucked up shit (2016) by cperciva on Sunday July 29, 2018 @10:36PM (#17641657)
The "Bell Curve" for females of a species generally has a significantly narrower standard deviation for practically any genetically driven characteristic.

Isn't this limited to traits which are influenced by XY chromosomes? (Usually due to males having only one X and thus being more likely to express recessive genes?)

Re:Signaling in tech is some fucked up shit (2016) by wellpast on Tuesday July 31, 2018 @12:15PM (#17654454)
I think there are much more to the dynamics than just genetic distributions. For instance, not every male and female are opting into tech careers; only those w/ interest and/or talent are pursuing tech careers--after this filter, for example, who knows what remains of any genetic distribution?
Re:Signaling in tech is some fucked up shit (2016) by __blockcipher__ on Sunday July 29, 2018 @06:47PM (#17640786)
Seems like an interesting assumption. I’m mot convinced there is a difference, but neither am I confident that there isn’t one.
Re:Signaling in tech is some fucked up shit (2016) by wellpast on Sunday July 29, 2018 @07:00PM (#17640848)
Yeah I have no instincts in this because my experience has always been so fewer women than men on the engineering team. So this is totally anecdotal. But the few women I’ve worked with have always been in the upper part of the talent scale, while there has been much variance among the men. I.e., I’ve encountered many low talent (and high talent) men but not one low talent woman. Maybe there are enough hurdles for women (even if the only hurdle is that there are so few _other_ women) that you kinda have to be interested & reasonably good at the job to stick around. If this is true the bell curves may be better for women applicants. However amy anecdotal experience could be simply wrong and it somehow is even or worse for women or something other like overlapping curves of different shapes.
Re:Signaling in tech is some fucked up shit (2016) by smhost on Sunday July 29, 2018 @07:30PM (#17640980)
From what we understand about the difference in white-collared intelligence in males vs females, there's a higher variance in intelligence among males than in females. So either women really are in general better at coding than men, or the mid-to-low skilled women aren't making it professionally as much as they should, and only the highest-skilled women are being selected. If your anecdote generalizes, that is. (FWIW, that's been my experience as well.)
Re:Signaling in tech is some fucked up shit (2016) by tptacek on Sunday July 29, 2018 @08:22PM (#17641221)
This logic comes up all the time on HN. I always wonder whether the people repeating it really believe that commercial software development is so intellectually challenging that it is only practiced by people at the very top end of the cognitive spectrum.
Re:Signaling in tech is some fucked up shit (2016) by smhost on Sunday July 29, 2018 @09:55PM (#17641542)
No, I was just wondering whether the mean for women is significantly to the right of the mean for men, or whether mid-to-low skilled women aren't being hired for some other reason (hiring bias, self-selection, or whatever). Or maybe my experiences don't generalize, and there actually are a bunch of mid-to-low skilled women whom I've simply never encountered.
Re:Signaling in tech is some fucked up shit (2016) by tptacek on Sunday July 29, 2018 @10:31PM (#17641641)
My subtext is that commercial software development is so cognitively unremarkable and routinized that you're not going to see any indication of male/female cognitive differences in the demographics of our field.

It's an argument that doesn't play well on message boards, because software developers love to believe that they're part of a cognitive elite "inventing the future" and "eating the world", when in fact really the overwhelming majority of us are performing a bog-standard white collar symbol manipulation job no more challenging than the job done by an accountant or actuary.

Nerds like to pretend that we're all working on the graph isomorphism problem alongside Babai, but really most of our days involve basic wiring of data from one place to another; form fields to database rows to packet fields to page markup. We want to believe we're brain surgeons, but most of the time we're barely even dentists.

Re:Signaling in tech is some fucked up shit (2016) by wellpast on Sunday July 29, 2018 @11:25PM (#17641820)
I love the deprecation bc I think we sw engineer’s deserve it to a degree.

But I will also say that various software shops I know of large and small are always desperate to find good talent. I’ve hired quite a bit myself and finding capable talent is very difficult. So our work is not as totally deprecatable as you make it out to be.

Re:Signaling in tech is some fucked up shit (2016) by tptacek on Sunday July 29, 2018 @11:31PM (#17641844)
Believe me, I don't doubt there's a skill to doing this stuff; I've dedicated a big part of my career to finding and assessing that skill. But there's skill and aptitude to all sorts of things, from legal work to baking. We don't often talk about how there are lots of men or women bakers due to the distribution of intelligence.
Re:Signaling in tech is some fucked up shit (2016) by JamesBarney on Monday July 30, 2018 @05:40PM (#17648316)
I imagine being a doctor is more selective for high IQ than development and there are just as many female doctors as male ones.

If this is a true effect I imagine it's a selection effect. Women who felt luke warm about coding never entered, or left.

Re:Signaling in tech is some fucked up shit (2016) by troupe on Sunday July 29, 2018 @06:59PM (#17640844)
If there was a difference, are you allowed to note it or will you get fired for it? Programming skill is hard to measure. Chess is an interesting area that is a bit easier to quantify.
Re:Signaling in tech is some fucked up shit (2016) by s3nnyy on Sunday July 29, 2018 @07:35PM (#17641008)
Some say "men are more interested in things and women are more interested in people" https://youtu.be/78ZfKUUsNcc?t=256

Given a woman in tech, you probably have someone who is at the tails, someone really good.

Re:Signaling in tech is some fucked up shit (2016) by lifeisstillgood on Sunday July 29, 2018 @06:43PM (#17640769)
Women in tech would presumably have the same signalling as Clojure users - greater probability of being competent ? Is that the point you were making?