Live data from Hacker News

I Won't Hire People Who Use Poor Grammar

blogs.hbr.org

91–100 of 334 posts

Re: I Won't Hire People Who Use Poor Grammar

#91
post #61

Earlier quoted context omitted.

It's more like I am applying for a programming job, and I don't see why I have to subject myself to your whims. Consider that instead of grammar, I am advocating I will only hire people who can do 50 push-ups. After all, what can I expect from people who are sloppy towards something as important their own bodies. What's so bad about 50 push-ups? Any fit person(excluding extenuating circumstances) should be able to do…

What? If you're writing software being able to produce clear documentation, write-ups, and other supplemental materials is quite important. In some cases, far more important than writing the actual code. In some hires I've used a descriptive writing assignment, where I ask the candidate to describe in words what they are looking at. You can learn much from these things, including: analysis skills, close looking, how…

> What? If you're writing software being able to produce clear documentation, write-ups, and other supplemental materials is quite important. In some cases, far more important than writing the actual code.

You are taking it to the extreme where there are only 2 states: grammar purists and monkeys banging at keyboard. Someone who mixes up "its" and "it's" is capable of all the important stuff you listed. I mix "its" and "it's" a lot while typing. I know the difference, my fingers don't.

> analysis skills, close looking, how they think, and, well, how well they would document their software.

And none of it is a result of good grammar. Are you implying that somehow good grammar leads to good analytic skills? Or are you saying talking with them gives you a window to their mind? If the latter, the window is wide open irrespective of how often I mix "it's" and "its". And how I prefer my period outside of quotes or parens(Why? Because I like it that way. That's why).

Re: I Won't Hire People Who Use Poor Grammar

#92
post #45

Earlier quoted context omitted.

But why change the spelling? Maintainance looks much more logically correct.

Because that's pronounced "maintain-ance". Stress on the "ain".

That sounds like a regional dialect. I've never heard it pronounced that way in the northeast US at the very least.

Re: I Won't Hire People Who Use Poor Grammar

#93

When I screen, interview and hire people, I look for reasons to hire someone as opposed to trying to find reasons to disqualify people. This kind of negative approach (especially when dealing with people) is just not a good way to go about things in my opinion and experience.

I'm sure you do both. Why would you ignore negatives?

Like "this guys skillset is great so were going to ignore that he was fired from his last job for laziness and that all his department left because of his sociopathic behaviour". Seriously?

Re: I Won't Hire People Who Use Poor Grammar

#94
Once again here on Hacker News we are talking about hiring procedures for technical companies. Many people find this topic interesting, because most of us have applied for a job at least once, and many of us have been in a position to recommend someone else for a job, or to hire someone for a job. From participants in earlier discussions I have learned about many useful references on the subject, which I have gathered here in a FAQ file. The review article by Frank L. Schmidt and John E. Hunter, "The Validity and Utility of Selection Models in Personnel Psychology: Practical and Theoretical Implications of 85 Years of Research Findings," Psychological Bulletin, Vol. 124, No. 2, 262-274

http://mavweb.mnsu.edu/howard/Schmidt%20and%20Hunter%201998%...

sums up, current to 1998, a meta-analysis of much of the HUGE peer-reviewed professional literature on the industrial and organizational psychology devoted to business hiring procedures. There are many kinds of hiring criteria, such as in-person interviews, telephone interviews, resume reviews for job experience, checks for academic credentials, personality tests, and so on. There is much published study research on how job applicants perform after they are hired in a wide variety of occupations.

http://www.siop.org/workplace/employment%20testing/testtypes...

EXECUTIVE SUMMARY: If you are hiring for any kind of job in the United States, prefer a work-sample test as your hiring procedure. If you are hiring in most other parts of the world, use a work-sample test in combination with a general mental ability test.

The overall summary of the industrial psychology research in reliable secondary sources is that two kinds of job screening procedures work reasonably well. One is a general mental ability (GMA) test (an IQ-like test, such as the Wonderlic personnel screening test). Another is a work-sample test, where the applicant does an actual task or group of tasks like what the applicant will do on the job if hired. (But the calculated validity of each of the two best kinds of procedures, standing alone is only 0.54 for work sample tests and 0.51 for general mental ability tests.) Each of these kinds of tests has about the same validity in screening applicants for jobs, with the general mental ability test better predicting success for applicants who will be trained into a new job. Neither is perfect (both miss some good performers on the job, and select some bad performers on the job), but both are better than any other single-factor hiring procedure that has been tested in rigorous research, across a wide variety of occupations. So if you are hiring for your company, it's a good idea to think about how to build a work-sample test into all of your hiring processes.

Because of a Supreme Court decision in the United States (the decision does not apply in other countries, which have different statutes about employment), it is legally risky to give job applicants general mental ability tests such as a straight-up IQ test (as was commonplace in my parents' generation) as a routine part of hiring procedures. The Griggs v. Duke Power, 401 U.S. 424 (1971) case

http://scholar.google.com/scholar_case?case=8655598674229196...

interpreted a federal statute about employment discrimination and held that a general intelligence test used in hiring that could have a "disparate impact" on applicants of some protected classes must "bear a demonstrable relationship to successful performance of the jobs for which it was used." In other words, a company that wants to use a test like the Wonderlic, or like the SAT, or like the current WAIS or Stanford-Binet IQ tests, in a hiring procedure had best conduct a specific validation study of the test related to performance on the job in question. Some companies do the validation study, and use IQ-like tests in hiring. Other companies use IQ-like tests in hiring and hope that no one sues (which is not what I would advise any company). Note that a brain-teaser-type test used in a hiring procedure could be challenged as illegal if it can be shown to have disparate impact on some job applicants. A company defending a brain-teaser test for hiring would have to defend it by showing it is supported by a validation study demonstrating that the test is related to successful performance on the job. Such validation studies can be quite expensive. (Companies outside the United States are regulated by different laws. One other big difference between the United States and other countries is the relative ease with which workers may be fired in the United States, allowing companies to correct hiring mistakes by terminating the employment of the workers they hired mistakenly. The more legal protections a worker has from being fired, the more reluctant companies will be about hiring in the first place.)

The social background to the legal environment in the United States is explained in many books about hiring procedures

http://books.google.com/books?hl=en&lr=&id=SRv-GZkw6...

http://books.google.com/books?hl=en&lr=&id=SRv-GZkw6...

Some of the social background appears to be changing in the most recent few decades, with the prospect for further changes.

http://intl-pss.sagepub.com/content/17/10/913.full

http://www.economics.harvard.edu/faculty/fryer/files/Fryer_R...

http://books.google.com/books?hl=en&lr=&id=frfUB3GWl...

Previous discussion on HN pointed out that the Schmidt & Hunter (1998) article showed that multi-factor procedures work better than single-factor procedures, a summary of that article we can find in the current professional literature, for example "Reasons for being selective when choosing personnel selection procedures" (2010) by Cornelius J. König, Ute-Christine Klehe, Matthias Berchtold, and Martin Kleinmann:

"Choosing personnel selection procedures could be so simple: Grab your copy of Schmidt and Hunter (1998) and read their Table 1 (again). This should remind you to use a general mental ability (GMA) test in combination with an integrity test, a structured interview, a work sample test, and/or a conscientiousness measure."

http://geb.uni-giessen.de/geb/volltexte/2012/8532/pdf/prepri...

But the 2010 article notes, looking at actual practice of companies around the world, "However, this idea does not seem to capture what is actually happening in organizations, as practitioners worldwide often use procedures with low predictive validity and regularly ignore procedures that are more valid (e.g., Di Milia, 2004; Lievens & De Paepe, 2004; Ryan, McFarland, Baron, & Page, 1999; Scholarios & Lockyer, 1999; Schuler, Hell, Trapmann, Schaar, & Boramir, 2007; Taylor, Keelty, & McDonnell, 2002). For example, the highly valid work sample tests are hardly used in the US, and the potentially rather useless procedure of graphology (Dean, 1992; Neter & Ben-Shakhar, 1989) is applied somewhere between occasionally and often in France (Ryan et al., 1999). In Germany, the use of GMA tests is reported to be low and to be decreasing (i.e., only 30% of the companies surveyed by Schuler et al., 2007, now use them)."

Integrity tests have limited validity standing alone, but appear to have significant incremental validity when added to a general mental ability test or work-sample test.

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

http://apps.opm.gov/ADT/Content.aspx?page=3-06&JScript=1

http://www.princeton.edu/~ota/disk2/1990/9042/9042.PDF

http://www.hotelschool.cornell.edu/research/chr/pubs/reports...

Bottom line: if someone is hiring for a company that produces technical documentation, a company like iFixit.com, and one feature of the product is grammatically correct writing, it's a reasonable subpart of a work-sample test to include testing for revising English prose. If someone is hiring for managing a jewelry store (a local example I know) or for building wood-frame houses, it's quite possible that a work-sample test would completely disregard the issue of correct spelling and grammar. I know a very successful owner of a jewelry store (I know him as a fellow soccer dad who once coached one of my children) who has quite dodgy spelling and grammar and punctuation, but who can communicate in written English for emailing people. I'm aware of multiple local carpenters and other people in construction businesses, including managing construction businesses, who have varying degrees of punctilious correctness in English writing, but all of them making their reputations and their livings by how they construct buildings, not by how they construct sentences. If writing is part of the work (even just for exchanging ideas with colleagues in memos or emails), sure, test it. If writing is not particularly part of the work, don't worry about it.

Re: I Won't Hire People Who Use Poor Grammar

#95
post #62
post #44

Earlier quoted context omitted.

What's so bad about a grammar test? Any competent person (excluding extenuating circumstances: dyslexia, etc.) should be able to pass a simple grammar test. It's not some hardship that you have to study for or anything.

What's so bad about it is that unfounded assumptions are being drawn from the performance of said test. Any competent person should be able to make a bed neatly and quickly. Would you apply for a (non-hospitalitly-related)job that required you to demonstrate your bed-making abilities?

This seems to imply that programmers never write natural language or that their ability to do so is unimportant.

If you're writing more code than natural language (documentation, discussion of specs, interaction with the team, etc) something is extremely wrong.

Re: I Won't Hire People Who Use Poor Grammar

#97

Earlier quoted context omitted.

Because that's pronounced "maintain-ance". Stress on the "ain".

That sounds like a regional dialect. I've never heard it pronounced that way in the northeast US at the very least.

I don't think anyone pronounces it that way, because what everyone is saying is the word that is spelt "maintenance".

If you were to actually pronounce the word that is spelt "maintainance", that is how it would be pronounced, with the stress on the "ain".

Re: I Won't Hire People Who Use Poor Grammar

#98
post #87
post #23

Earlier quoted context omitted.

> If the answer is "yes" to both of these then I would assume that the people who pass the test are English majors with minors in Linguistics ;-) I don't know. I am not a native speaker, and am not an English major, but the answer is "yes" to both of them. Am I understanding you correctly that you are saying people can't make out active and passive between "I wrote a letter", "A letter was written by me"? "Who" and "…

"Whom" is also almost impossibly archaic and no longer considered part of modern English (having almost completely fallen out of usage around the start of the 20th century). It survives almost entirely in discussions of when to use it and almost never appears in modern writing except as a demonstration of what linguists call a "prestige form". "To whom did you give it?" vs. "Who did you give it to?" the latter is mor…

Huh. Really? I use whom all the time, and most of my friends do as well. Granted, a) we're all snobs, and b) we don't use it in every case we should, but we still use it.

Maybe we're part of this little post 2000 resurgence: http://books.google.com/ngrams/graph?content=whom&year_s...

Re: I Won't Hire People Who Use Poor Grammar

#99
post #12

I agree. I think Eric S. Raymond nails it: "While sloppy writing does not invariably mean sloppy thinking, we've generally found the correlation to be strong — and we have no use for sloppy thinkers." http://www.catb.org/~esr/faqs/hacker-howto.html

I agree with this. There's also a strong correlation between sloppy writing and poor reading comprehension. This is usually someone who never takes time to sit down and read edited or well-crafted prose.

Why is good reading comprehension important for programmers? You see it often: A fellow programmer complains they can't find an answer to a particular problem they're having, even when the solution is staring them right in the face in the first Google search result. Good reading comprehension helps you help yourself.

Re: I Won't Hire People Who Use Poor Grammar

#100
post #81
post #32

Earlier quoted context omitted.

Saving the google search for people who don't know what an oxford comma is. http://en.wikipedia.org/wiki/Serial_comma "Portugal, Spain, and France" (Oxford comma) "Portugal, Spain and France" (Not Oxford comma)

Even oxford discourages its use in public writing. http://www.ox.ac.uk/public_affairs/services_and_resources/st...

But the Chicago Manual of Style encourages its use - this isn’t a closed book. Which the wikipedia article points out.
Post reply on HN