News for hackers. Stuff that matters.
Re:Ask HN: How do detect a crappy boss / toxic environment w... by EliRivers on Thursday April 07, 2016 @03:55PM (#11450125)
Only on HN could someone argue that trying to select smart employees for technical jobs is a bad idea.
Re:Ask HN: How do detect a crappy boss / toxic environment w... by pfooti on Thursday April 07, 2016 @08:48PM (#11451850)
So the thing is, "smart" is a pretty sloppy term. Furthermore, claiming that measuring this "smartness" in a small-sample, unrelated set of tasks (a relaxed, 30 question test), and that this "smartness" on the test would transfer to "ability to write good code well and work in a team" is utter crap.

Doing well on a test is usually an indicator that you do well on that kind of test. Even good psychometrics tend to fail with calibration problems - the vast majority of these tests were written and calibrated using psychology undergraduates at western universities. That's a significant sampling problem. [0]

So I'm personally not opposed to selecting for "smart" employees. But I do think that the belief that a short test actually selects for that kind of smartness in any meaningful way is sloppy thinking.

0: http://blogs.scientificamerican.com/primate-diaries/the-weir...

Re:Ask HN: How do detect a crappy boss / toxic environment w... by geofft on Thursday April 07, 2016 @09:13PM (#11451935)
I would much rather work with a team of people of average intelligence, with humility, work ethic, honest enthusiasm, empathy, etc., than with a team of brilliant people with none of those things. That goes double for technical jobs where you're building a complicated product over the long term. We're not here to solve the Putnam and go home. We're delivering value, and that involves solving a hard problem simply because there is no easier way, not because hard problems are inherently worth working on.
Re:Ask HN: How do detect a crappy boss / toxic environment w... by EliRivers on Friday April 08, 2016 @07:42PM (#11459015)
You people just read your own prejudices into everything.
Re:Ask HN: How do detect a crappy boss / toxic environment w... by rnovak on Thursday April 07, 2016 @06:51PM (#11451329)
So according to you, doing mediocre on an IQ test makes someone not smart, right?

What about people with dyslexia (such as myself)?

What about people who have test-anxiety?

They aren't arguing that hiring smart people is a bad idea, they're saying being dismissive and discriminatory is a bad idea (and illegal, in the US - violation of the ADA).

Re:Ask HN: How do detect a crappy boss / toxic environment w... by sheepleherd on Thursday April 07, 2016 @07:39PM (#11451570)
So, you think that hiring smart people is a good idea, and you think that people who do well on IQ tests are smart, and you think that people who are not smart do poorly on IQ tests, but you are adding that there are some additional smart people who don't do well on IQ tests, and you are rightfully concerned because you consider yourself to be one of them, and you think there are laws that put the burden of uncovering these people on private employers? I'm not sure that's true, but anyway, just wanted to clarify.

Out of curiosity, this is a serious question: are you a programmer and if so does dyslexia cause you problems coding? lots of library functions can have confusingly similar names and spellings for me, and I don't have any reading problems.

Re:Ask HN: How do detect a crappy boss / toxic environment w... by eric_h on Thursday April 07, 2016 @05:52PM (#11451002)
If I may pick a small nit. People who get good grades are "smart", people who score highly on IQ tests are "intelligent" - those characteristics are essentially orthogonal. It is generally easier for intelligent people to get smart, but they can just as easily get stupid.

Generally speaking, good developers are both smart and intelligent.