News for hackers. Stuff that matters.
Re:I Won't Hire People Who Use Poor Grammar by irahul on Friday July 20, 2012 @09:13AM (#4270550)
My train of thoughts:

> Everyone who applies for a position at either of my companies, iFixit or Dozuki, takes a mandatory grammar test.

Whoa. Who do you think you are - google? What makes you think I am going to sit through your grammar test? If I am agreeing to your grammar test, either you are one of the most desirable places to work for(never heard of you), or economy is about to collapse and this is the only job I can find, or I am so incompetent and/or desperate that I will take anything that comes my way(beggars, choosers etc).

> Of course, we write for a living.

Oh, should have mentioned it earlier. I won't have gone into internal monologue.

> But grammar is relevant for all companies.

May be it is. But not as relevant as you make out to be.

> In blog posts, on Facebook statuses, in e-mails, and on company websites, your words are all you have.

Apart from my words, I have my intent, thoughts, opinions, facts. Words are a medium. You are giving them undue importance. If I am reading an article about face recognition using opencv, I am interested in code snippets and concepts. My mind auto-correct "there, their, they're" or "its, it's". If I am reading about "infant mortality rate in India", I am interested in figures, reasons, solutions. That is not to say grammar or writing style doesn't matter. I am saying it's not as important as you put it to be, and good writing doesn't automatically come with proper grammar.

> If it takes someone more than 20 years to notice how to properly use "it's," then that's not a learning curve I'm comfortable with.

You are assuming someone good at something is assigning equal amount of weight and is equally interested in grammar as he is in whatever he is good at. I know good programmers who write weird English. Anecdote, data etc. Neither of us have data, anecdotes don't count for much.

> So, even in this hyper-competitive market, I will pass on a great programmer who cannot write.

Don't worry about it. To pass on a great programmer, you will have to get them interested in you first. It's a win-win situation. They aren't going to flock to your offices to take your grammar test, and you won't have to pass on great programmers due to bad grammar.

> Grammar signifies more than just a person's ability to remember high school English. I've found that people who make fewer mistakes on a grammar test also make fewer mistakes when they are doing something completely unrelated to writing — like stocking shelves or labeling parts.

Citations please. Also, unless you are stocking shelves, how does it matter? Never came across a programmer whose desk is always messy(I never came across one whose desk is clean)?

> In the same vein, programmers who pay attention to how they construct written language also tend to pay a lot more attention to how they code.

Citation please. And how do you know it's not the other way round?

> And I guarantee that even if other companies aren't issuing grammar tests, they pay attention to sloppy mistakes on résumés. After all, sloppy is as sloppy does.

I am all for proof reading resumes and cover letters, but "sloppy is as sloppy does" assumes someone who is sloppy at something is sloppy at everything. That's as far from the truth as it can be.

> Grammar is my litmus test.

You must be fun to work with. A CEO whose litmus test to hir a programmer isn't programming finesse or cultural fit or drive..., but how good is his grammar.

Re:I Won't Hire People Who Use Poor Grammar by nirvdrum on Friday July 20, 2012 @09:47AM (#4270748)
My issue is if you're unable to delineate between "it's" and "its" and it's the language you've been speaking natively for the past 25 years, I tend to doubt your ability to know what form of "const" to use in C++. At the very least, lack of proofreading suggests to me you might be rash with your code as well.

Many disagree with me on this point of view, but routinely I've found that those that express themselves well in their native language write better code. That may be a self-reinforcing feedback loop because a lot of bad projects have a lot of terrible or non-existent documentation. And on a personal level I don't want to work with someone that communicates like a tween (NB: I'm not saying that you do, but I've run across it many times).

I also take a lot of issue with the "you know what I mean so you're being a pedant" retort. Not only is it wholly counter-productive, but it's not even accurate when you're talking about globally connected people. Quite frequently a non-native speaker will stumble upon what is written and be thoroughly confused.

Re:I Won't Hire People Who Use Poor Grammar by irahul on Friday July 20, 2012 @10:36AM (#4270979)
> My issue is if you're unable to delineate between "it's" and "its" and it's the language you've been speaking natively for the past 25 years, I tend to doubt your ability to know what form of "const" to use in C++.

Eh, how about asking me about const-correctness than inferring from my use of "it's" and "its"? You know, you can actually talk about const-correctness instead of inferring from the grammar test.

> At the very least, lack of proofreading suggests to me you might be rash with your code as well.

It's hard to be rash with code if you aren't copy pasting. It isn't the same as posting comments on HN.

> And on a personal level I don't want to work with someone that communicates like a tween

As I already said elsewhere, you are assuming things to be binary when they are not. The spectrum between "liek dis if u cry everytim" crowd and "People with bad grammar should be hanged" people is quite wide.

> Quite frequently a non-native speaker will stumble upon what is written and be thoroughly confused.

Not an excuse for bad grammar, but a non-native speaker is fine with both "didn't go" and "didn't went". I don't see how he is going to be confused. Non-native speakers are confused when they encounter phrases, idioms and slangs they don't know. Fun exercise - ask an Indian if he/she would like to go out with you sometime. He/she would most likely say yes/no without understanding what you meant. Do you have any examples where simple grammar mistakes confuse non-native speaker? I am a non-native speaker, and am curious to know.

Re:I Won't Hire People Who Use Poor Grammar by nirvdrum on Friday July 20, 2012 @11:05AM (#4271098)
While I could exhaustively ask about every aspect of every language you might have to work in, it's far simpler to use a proxy. The proxy in this case is your native language and seems to work rather well. And since your job certainly isn't going to be writing code for 8 hours straight, the ability to communicate well is a good skill to have.

For what it's worth, I use other aspects to proxy fit and ability as well. If you can't bother to clean up before an interview, I have a pretty reasonable idea of how you conduct yourself.

Re: the non-native speaker part. I've had to help a lot of people out over the years on various support channels because someone wrote "then" instead of "than" or "loose" instead of "lose." Since many people seem to be able to read & write in foreign languages but not necessarily speak them, homophones are easily confused. Personally I know enough French & German to follow along with most technical materials, but easily get derailed by misspellings. Is it an idiom I'm unaware of? Is it a word I don't know? Is it some sort of slang?

Re:I Won't Hire People Who Use Poor Grammar by irahul on Friday July 20, 2012 @04:00PM (#4272628)
> The proxy in this case is your native language and seems to work rather well.

No, it does not. The very notion that someone who always uses "its" and "it's" understands const-correctness is ridiculous.

Command over native language doesn't signify programming prowess. You are imagining things or extrapolating your personal anecdotes to absolutes. Please provide citations if it's a proven fact.

> For what it's worth, I use other aspects to proxy fit and ability as well. If you can't bother to clean up before an interview, I have a pretty reasonable idea of how you conduct yourself.

What on earth does cleaning up mean? I shower in the morning. I am not going to take a special shower for you. Whether or not I shave depends on my mood. I don't see how on earth an interview with you should affect my facial hairs. I am not coming in looking like a hobo, and anything beyond that isn't your call at all.

Why the hell people count on metric which doesn't indicate a person's qualities relevant to the job? Whatever the fuck happened to phone screening, checking up open source projects, on-site problem solving, having a conversation, checking up references. Where and why the fuck wearing a suit or taking a grammar test came into picture?

Re:I Won't Hire People Who Use Poor Grammar by vehe on Friday July 20, 2012 @06:56PM (#4273248)
I think someone else pointed it out, it's a cultural affinity test. The shit about grammar indicating code quality is just rationalization for wanting someone who is culturally similar to you - has the same values as you. That is, someone who holds arbitrary things like grammar, facial hair, etc. in the same value as you do.

Some of my coworkers are from India and China. I could make up similar things about how chewing with your mouth open and not wearing deodorant indicates a lack of awareness of manners and means they are unaware of memory leaks and race conditions in their code.

It's on me to come to terms with people chewing with their mouth open, not fire them because of subconscious cultural supremacy issues.

Re:I Won't Hire People Who Use Poor Grammar by nirvdrum on Friday July 20, 2012 @07:38PM (#4273381)
No, it's as I stated initially. If you're unable to keep track of the rules of your native language, something that should be second nature, I have severe doubts about your ability to keep track of the rules in Scala, Ruby, or whatever else. If it's simply that you don't proofread or don't care to, I have no reason to believe you'll do so when dealing with code. That problem is exacerbated in dynamic languages where typos won't be caught until runtime. Both writing natural language and code are forms of expressing ideas, problems, & solutions cogently -- you just have different grammar forms for the various languages, each with their own rules. The two are even merging with things like Cucumber.

No, I don't have exhaustive studies on this. That neither proves nor disproves anything. I never stated any of this beyond my own opinion, which has been formed and reinforced by 15 years of working in open source, running & working at startups, and working at big companies.

That aside, code is typically only part of your job. Documentation, blog posts, interacting with customers, partners, team members, etc. are all part of engineering. You don't have to like it or think it's just, but people do and will form opinions about you on this stuff. Many times it won't be other engineers, which you may be fine with, but engineering alone often doesn't make a successful business. You can disagree with it or be flippant about it, but it really doesn't change reality.

Re:I Won't Hire People Who Use Poor Grammar by vehe on Friday July 20, 2012 @07:44PM (#4273402)
> If it's simply that you don't proofread or don't care to, I have no reason to believe you'll do so when dealing with code.

Really. So all past experience on a person's resume doesn't count toward that? Every other aspect of your interview with that person cannot possibly lend anything to increase your belief that they proofread their code? That is quite irrational.

It's also irrational to assume that because someone doesn't keep track of grammar rules, that they are unable to do so. That's a pretty big mistake of an assumption.

Re:I Won't Hire People Who Use Poor Grammar by Graham24 on Friday July 20, 2012 @11:30AM (#4271207)
tut, tut. "People with bad grammar should be hung".
Re:I Won't Hire People Who Use Poor Grammar by stan_rogers on Friday July 20, 2012 @11:39AM (#4271246)
It should be hanged, actually, when referring to capital punishment, except when drawing and quartering are involved. It's a quirk of the language; hung is correct in most circumstances.
Re:I Won't Hire People Who Use Poor Grammar by excuse-me on Friday July 20, 2012 @11:48AM (#4271300)
Yes we know, that's what made the comment funny - now you've spoiled the joke.
Re:I Won't Hire People Who Use Poor Grammar by stan_rogers on Friday July 20, 2012 @12:47PM (#4271642)
You seem to be using the word funny in a sense with which I am not at all familiar. Again, consider the non-native user of English, and the likelihood of encountering him or her on a site like this. "Ironic" grammar policing without an irony indicator isn't at all funny.
Re:I Won't Hire People Who Use Poor Grammar by halefx on Saturday July 21, 2012 @04:29AM (#4274337)
Is now a good time to point out that "poor" would be more appropriate than "bad" and that it should be reworded not to use "with"?
Re:I Won't Hire People Who Use Poor Grammar by irahul on Friday July 20, 2012 @03:46PM (#4272574)
Am I missing the joke?

People are hanged, portraits are hung.

Re:I Won't Hire People Who Use Poor Grammar by sampo on Friday July 20, 2012 @11:09AM (#4271109)
As a non-native speaker of English, I have been wondering how much signal it would be appropriate for me to infer from the kind of sloppy grammar that is typical only for native speakers of English? [1]

I learned English at school as a second language, and we would always start with the written form, and then learn how to pronounce. So my "hash table" is primarily organized based on the written form, and it would be impossible for me to mix "two" and "too", "they're" or "their" or "there", or "its" and "it's" [2]. I hadn't even realized that "too" and "two" are pronounced the same, before a native speaker pointed it out to me, as my hash table doesn't support that kind of searches.

Also my native language (Finnish) uses a (nearly) phonetic writing, so phonetic misspelling of words is mainly restricted to people with no high school level of education, and who didn't do that well in primary school either.

I do, like the writer of the liked article, get that feeling of sloppiness, when I see those spelling or grammar mistakes in English text, but I don't really know how much signal it would be appropriate for me to infer from them?

I probably should not use as harsh standards as I do with Finnish, since those misspellings seem relatively common in English in the web.

[1] Well, typical of people who learned spoken English before written English, but in the modern world this pretty much coincides with native speakers.

[2] Well, "it's" and "its" is maybe a border case, maybe not totally impossible to mix those two, just very unlikely.

Re:I Won't Hire People Who Use Poor Grammar by HeyLaughingBoy on Friday July 20, 2012 @01:12PM (#4271791)
My gut tells me (there's a scientific statement, if ever there was one!) that it correlates mainly to people who haven't read much in print. Print publications tend to be edited better than online ones. Unfortunately, bad spelling is reinforced by spending a lot of time online and being exposed to misspellings that are not corrected.

As a child I didn't have access to TV, so I read everything in sight and I read constantly. The end result is I have a particularly sensitive eye for spelling and grammar mistakes. I find the misuse of, e.g., "loose" instead of "lose," to be tremendously irritating. The people I know who read a lot simply don't make trivial mistakes like that unless they're in a hurry and mistype.

Is it sloppy? I would say it's sloppy if writing is a large part of your job. Otherwise, it's mainly an indicator of someone who doesn't read print very much.

It is also getting worse at an increasing rate. I remember when mispelled words and bad grammar in reputable magazines and journals was rare, now it's almost expected that anything I read will have a few.

Re:I Won't Hire People Who Use Poor Grammar by olivier1664 on Wednesday July 25, 2012 @10:48PM (#4294143)
Don't forget dyslexic guy: it makes your indicator wrong. According a fast google research, it's 5% of people.
Re:I Won't Hire People Who Use Poor Grammar by pka on Friday July 20, 2012 @11:47AM (#4271286)
Absolutely agree. I would never be able to take anybody seriously (in terms of hiring them) who can't spell or get basic grammar right in my native tongue, but this tends to be quite common in written English.

How much can one infer from the fact that a native speaker mixes up "they're" and "their"?

Re:I Won't Hire People Who Use Poor Grammar by einhverfr on Friday July 20, 2012 @11:23AM (#4271168)
This is interesting.

On the other hand, I would like to know since Finnish as a language fascinates me:

How common are noun-case errors among people who have a high school education? I mean something like using the elative case when the ablative might be more appropriate?

Re:I Won't Hire People Who Use Poor Grammar by sampo on Friday July 20, 2012 @11:39AM (#4271245)
How common are noun-case errors among people who have a high school education? I mean something like using the elative case when the ablative might be more appropriate?

Nonexistent. I don't think even preschool children ever mix those. I don't have kids, so I can't say how it is with the kids who are just learning to speak.

Also in English, you don't see people mixing "into" and "onto" even remotely as often as the mistakes the linked article talked about.

Re:I Won't Hire People Who Use Poor Grammar by michaelcampbell on Saturday July 21, 2012 @10:48AM (#4274864)
> My issue is if you're unable to delineate between "it's" and "its" and it's the language you've been speaking natively for the past 25 years,

I know the difference, and when I make a mistake I've found that every time it's been a mistake of my "finger muscle memory" when typing it rather than using the wrong word. In other words, I used the correct word, but I typed it incorrectly.

That is impossible to detect on any test where the answer is typed. Perhaps a followup to these sorts of tests are, "Here are all the places you used `its` and `it's`. Do you think they are all correct, and if not, which would you change?"

Re:I Won't Hire People Who Use Poor Grammar by gizmo686 on Friday July 20, 2012 @11:47AM (#4271291)
>"My issue is if you're unable to delineate between "it's" and "its" and it's the language you've been speaking natively for the past 25 years, I tend to doubt your ability to know what form of "const" to use in C++. At the very least, lack of proofreading suggests to me you might be rash with your code as well."

The difference is that const makes sense.

"Its" is the plural of "it", although we seem to use "they". "It's" is the possesive of "it", although we seem to use it as "it is". "It is" is proper English,although we tend to write it in slang "it`s". My use of punctuation respects the content of the quotations as the objects they are, although we seem to imply that "it" is spelled "it.".

Re:I Won't Hire People Who Use Poor Grammar by excuse-me on Friday July 20, 2012 @11:51AM (#4271315)
I would say mixing up its and it's is a sign of a good programmer!

Apostrophe-s means a possessive most of the time, so logically belonging to it should be it's. programmers like logic, if the English language happens to have case this wrong that's their problem!

Re:I Won't Hire People Who Use Poor Grammar by nirvdrum on Friday July 20, 2012 @11:56AM (#4271349)
I like to amuse myself thinking of people trying to use "her's," "his'," "their's," "our's," or "your's." The possessive form is pretty consistent with pronouns.
Re:I Won't Hire People Who Use Poor Grammar by excuse-me on Friday July 20, 2012 @12:00PM (#4271366)
The reasons for those are interesting - all to do with losing cases when middle English simplified and having to fit a few borrowed Norse words into Old English's German grammar.
Re:I Won't Hire People Who Use Poor Grammar by drivingmenuts on Friday July 20, 2012 @11:42AM (#4271265)
Here's a thought: you're assuming I care equally about grammar and programming.

If I use the wrong form of "it's" in a sentence, someone might wince somewhere (possible even rage a bit). No one is going to die.

If I use the wrong form of const, it's possible that all hell will rain down upon the Earth and millions will die in horrible gut-wrenching pain, clasping their loved ones to their chest and bemoaning the gods (the desirability of such an outcome is a wholly different matter).

The two issues do not equate at all.

ED: fixed spelling of "grammar".

Re:I Won't Hire People Who Use Poor Grammar by HeyLaughingBoy on Friday July 20, 2012 @01:18PM (#4271829)
No one is going to die

Since you brought it up...

I am a software developer for a medical device manufacturer. Poor spelling and grammar can change the meaning of a requirement, leading to a software error. Down the road someone can certainly die.

More likely, however, is that grammar and spelling errors in Requirements, Design, Procedure or other documents, or in code commit comments, or code comments themselves implies to an auditor for a Regulatory Body that our code itself is sloppy. That leads the auditor to dig deeper. Dig deep enough and you will find enough to hang someone.

For just this reason, we must pay attention to proper documentation, down to appropriate word choice. No, we don't test for usage of written English during interviewing, but it's strongly enforced during day-to-day work.

Re:I Won't Hire People Who Use Poor Grammar by eropple on Friday July 20, 2012 @12:38PM (#4271592)
If you don't care equally about grammar and programming, then you aren't wanted. You can no doubt latch onto a dev shop that doesn't care about that.

I don't see the problem and I admire the attitude. Use of the written word is important and, aside from the exceptions mentioned in the article, I think significantly less of people who don't write or speak well. It's important to me to work with good communicators and you can't be a good communicator if you can't speak and write well.

Re:I Won't Hire People Who Use Poor Grammar by nessus42 on Friday July 20, 2012 @02:47PM (#4272301)
> Many disagree with me on this point of view, but routinely I've found that those that express themselves well in their native language write better code.

Many people with perfect grammar communicate terribly, and many people with much less than perfect grammar communicate very effectively. If effective communication is important for a job position, perhaps looking directly for that skill would be more productive and fair?

Re:I Won't Hire People Who Use Poor Grammar by nirvdrum on Friday July 20, 2012 @07:41PM (#4273393)
Effective communication is important for every job position I've ever encountered. Whether it was when I was a porter at Dunkin' Donuts, a research assistant, a cog in the wheel at Cisco, or running my own company. At the very least, you need to be able to communicate effectively with the rest of your team and usually across departments.
Re:I Won't Hire People Who Use Poor Grammar by kamaal on Friday July 20, 2012 @10:46AM (#4271008)
>>I've found that those that express themselves well in their native language write better code.

If this is true, then apart from US and UK people who write good code don't exist elsewhere???

Its difficult to take you seriously after reading this.

Re:I Won't Hire People Who Use Poor Grammar by nirvdrum on Friday July 20, 2012 @10:55AM (#4271046)
Huh? I never said you had to communicate well in English. Even in your quoted text you can see that I said "in their native language."

And clever use of "its" there :-)

Re:I Won't Hire People Who Use Poor Grammar by nessus42 on Friday July 20, 2012 @12:52PM (#4271674)
Personally, I feel that to focus on trivialities such as the difference between "it's" and "its" to be morally indefensible. It's like being unwilling to hire people who are blind or deaf, or who need a wheel chair. (Uh oh! Is "wheel chair" one word or two? Or maybe it's hyphenated–oh no! I'm going to get fired!)

There are plenty of people who are quite smart and motivated, but are borderline dyslexic. Or maybe even not so borderline. For instance, I fully know the difference between "it's" and "its", and between "there", "their", and "they're". But I can stare at a paragraph for an hour and not be able to see such subtleties. Or sometimes even notsosubtle-ies. It's quite frustrating. And now I'm allegedly a poor employee to boot. Fan-fscking-tastic.

On the other hand, I am rather galled whenever I drive by the restaurant named "Your's".

Edit: I'd be willing to bet good money that whoever voted me down is not dyslexic. And despite making such mistakes frequently, I've often been commended for my clear writing. I received the highest grade given in several years in Creative Writing in college, got above 700 on my verbal SAT, and graduated from MIT. And yet some people want to judge me on whether I might type "it's" for "its" sometimes, and then utterly discount my opinion on that issue. Oy!

Re:I Won't Hire People Who Use Poor Grammar by nirvdrum on Friday July 20, 2012 @01:27PM (#4271867)
I didn't downvote you, but my guess is you were downvoted for making a rather tenuous and almost insulting relationship. There's a big difference between someone with an actual disability and those that just don't care about what they write. And I don't think anyone is even advocating for a zero tolerance policy. People make mistakes all the time. But calling it a "typo" or a triviality or otherwise getting defensive really doesn't help anything. It does however suggest how you might react when a "triviality" comes up in a codebase.
Re:I Won't Hire People Who Use Poor Grammar by nessus42 on Friday July 20, 2012 @01:55PM (#4272017)
I've never been diagnosed with a disability, and now I am supposed to jump through hoops to try to prove to people that I should be given some sort of special exemption? As if I need more humiliation in my life than to notice after the fact that what I've written is riddled with unintended little mistakes?

As to people caring about what they write: The litmus test should be whether they can effectively communicate, not whether they have the same arbitrary bees in their bonnets that someone else has. I might not want to hire anyone who can't give me their opinion on whether or not Frege would have discovered Godel's Incompleteness Theorem decades before Godel, if Frege hadn't been so discouraged by Russel's Paradox as to give up his entire endeavor to derive math from logic. After all, someone who hasn't put in the effort to study even the basics of modern philosophy can't be trusted to really think deeply on any issue, can they?

This, no doubt, is true, but it would also be a morally indefensible hiring practice.

As for making tenuous and almost insulting relationships: I find your claim that there is any correlation between having issues with "its" vs "it's" and the like, and the care with which one puts into their code, to be a tenuous and insulting claim. You're insulting my code-writing ability, and you've provided no evidence for your claim. That's pretty tenuous. You've also confounded caring with performance. Although it may or may not be the case that caring is a general personality trait that spans across all one's skills, performance can be quite different between skills.

As to whether such grammatical distinctions are trivial, I assure you that they are. Having some linguistics background, I feel qualified to assert this. (MIT degree in cognitive science.) If we were to all agree today to just use "its" all the time, rather than using both "it's and "its", the world would be no worse off.

P.S. I do know how to use const in C++.

Re:I Won't Hire People Who Use Poor Grammar by nirvdrum on Friday July 20, 2012 @02:15PM (#4272139)
Whenever you confuse the two, you cause me to have to reparse the sentence. "it's" becomes "it is" and then I have to determine that that doesn't make any sense and go back to substitute it. Vice versa. I also have a linguistics background. So I guess we'll have to agree to disagree.
Re:I Won't Hire People Who Use Poor Grammar by nessus42 on Friday July 20, 2012 @02:35PM (#4272236)
> Whenever you confuse the two, you cause me to have to reparse the sentence. "it's" becomes "it is" and then I have to determine that that doesn't make any sense and go back to substitute it.

I'm sorry. When they come up with a cure for dyslexia, I'll be sure to get it. In the meantime, I suspect that most people are just dyslexic enough (dyslexia is a spectrum) that these little things cause them a great deal of trouble. It's not that they don't care; it's that if they did care, it would drive them crazy. Me, I do care about details. That's no doubt, in part, why I became a programmer.

As to throwing you off, since this mistake is so common, it would seem to be easy enough to train yourself to treat the two words as hominyms of each other. After all, you have no problem, I take it, with all the other homonyms in the language. (Yeah, I know, wheelchair ramps are annoying!) The fact that the words are pronounced identically proves conclusively that we don't need the words to be distinguished, other than by context.

As to having linguistics backgrounds, in my classes they beat prescriptivism out of me. How did yours survive?

Re:I Won't Hire People Who Use Poor Grammar by nirvdrum on Friday July 20, 2012 @07:44PM (#4273400)
I guess I kept mine in tact by studying other languages and having to deal with people internationally. And my fondness for "The Elements of Style" and "On Writing" fostered it natively.
Re:I Won't Hire People Who Use Poor Grammar by nessus42 on Friday July 20, 2012 @09:35PM (#4273647)
I should think that dealing with people internationally would provide more tolerance for questionable grammar, not less, since non-native speakers of English typically make quite a few grammatical errors. Especially for irregular and idiomatic aspects of grammar.

Take those ignorant Brits, for example. They are always saying "different to" rather than "different from". That's much more annoying than using "it's" for "its", as it's not even pronounced the same way. And don't get my started on them misspelling "color" and "rumor".

Re:I Won't Hire People Who Use Poor Grammar by nirvdrum on Saturday July 21, 2012 @11:53AM (#4275004)
I've mentioned this elsewhere in the comments, but you're extremely unlikely to ever see a non-native speaker write "greater then" rather than "greater than." It's a pseudo-homophone (they really are pronounced differently) that just doesn't exist to anyone picking up English as another language. More than that, it's confusing as hell for them to read because it's a form that makes no sense. "would of" and "would've" is another that comes to mind. Mixing "lose" and "loose" up seems fairly common nowadays, too.

You're right in that those not fluent in English make mistakes that seem odd, but I don't think I've ever come across a case where the error wasn't with a different tense or form of the verb. I.e., the sentence is structured a bit oddly, but it largely makes sense. The same cannot be said of "would of."

Re:I Won't Hire People Who Use Poor Grammar by nessus42 on Saturday July 21, 2012 @07:09PM (#4275962)
> I don't think I've ever come across a case where the error wasn't with a different tense or form of the verb. I.e., the sentence is structured a bit oddly, but it largely makes sense.

Oh come now. English, and I presume all natural languages, are replete with idiom for which it is virtually impossible for a non-native speaker to ever master. (E.g., "different from" is the correct idiom, while "different than" is not. But non-native speakers often mess up idioms that I didn't even realize were idiomatic until I hear a foreign speaker get them wrong. Things like "Put that at the table" rather than "on the table", etc.) If you learn a language after puberty, you will almost certainly never learn a language with the fluency of a native speaker. Something in our brains restructures itself after that point.

And this is why your claim is so insidious. If someone grows up in a poor community which speaks a different dialect of English from "Standard Written English", and they don't become fluent in Standard Written English before the age of puberty, they are likely screwed for life. They are biologically determined to NEVER master it to the degree that you require. But since you have a background in Linguistics, you must already know this.

This whole topic makes me rather depressed. It seems to me that anyone who promotes the idea that anything like perfect grammar is required to be a programmer--or anything other than an editor of some sort--is lacking in both compassion and ability to think scientifically. If you are willing to discriminate in hiring based on hypotheses for which there is ZERO scientific evidence, then you fail on both counts.

In fact, if I were to hire programmers, I think that instead I might test them on their abilities to be empathic and to think scientifically and logically, since these are skills that actually do matter for software engineers. Prescriptive grammarians would fail on all three counts.

By the way, do you have any idea how hard it was to get into and graduate from MIT being dyslexic? And yet now the world wants to add all these crazy hiring criteria hoops that I'm supposed to jump through??? Coding on whiteboards? Having perfect grammar? Doing handsprings and cartwheels? Haven't I proven myself enough already by getting into and graduating from one of the best and most difficult universities in the world, and then continuing on in a career with many commendable accomplishments? E.g., writing the software that configures an X-ray space telescope, and implementing the specificity scoring algorithm for RNA Interference hairpins; knowing how to program in a dozen-plus programming languages; etc. The increasing tendency towards myopic monoculture and inflexible hiring practices infuriates me. I consider it a personal attack on my mental and financial well-being. And it is!

Regarding your claim that "would of" makes no sense, I'm not sure how to jibe this with your claim of having a linguistics background. The first thing that one learns in Linguistics, which is the scientific study of how people actually do speak, as opposed to the unscientific field of prescriptive grammar, which aims to tell people how they ought to speak, is that if a community of people speak or write a certain way, then it always makes sense, and there is always a good cognitive reason for it.

That's not to say that the good cognitive reason always maximizes functionality, but the same criticism can certainly be made about prescriptive grammar too. A lot of the rules in prescriptive grammar are completely arbitrary, and don't reflect the real language, as actually spoken.

A clear example of this is the deprecation of double negatives. This prohibition is a modern invention, invented by Bishop Robert Lowth in 1762. Before that everyone in English said, "I don't have none", just as they do in Romance languages. There was nothing wrong with the sentence, "I don't have none" before 1762, and there is nothing wrong with it today, except to the extent with which you wish to distinguish yourself as part of the upper class. This cynical reason is the very reason that most of Lowth's silly invented rules were adopted by the upper class. There was nothing better about the way Lowth wanted people to speak compared to the way they had spoke before, other than as tool of class distinction.

Another example is the word "ain't". The sentence, "Ain't I a genius?" is actually grammatically correct. Contrast this with how most people now will say, "Aren't I a genius?" which is just plain wrong. Why do people make this mistake? Because prescriptive grammarians beat "ain't" out of them, which caused people to start using something wrong. Sure, now the "correct" thing to say is "Am I not a genius?" But what kind of pretentious idiot would say that?

As to what sense there is to be made of "would of" and "it's" vs "its": This clearly expresses a natural human tendency to desire a more phonetic written language. Spelling in English is just plain dumb. Don't take my word for it--just ask the great author George Bernard Shaw.

I have friends from Italy, and they tell me that there are no such things as spelling bees in Italy. I.e., if you know how to pronounce a word, you know how to spell it. What an enlightened language! Perhaps without having to devote so much of their brains to keeping track of the spellings of tens of thousands of words, they can use it for more productive endeavors. I guess I have no scientific evidence for this, but I do hear that Italians are better lovers. That's gotta count for something!

tldr: A pox on the anti-scientific prescriptivists and obstacle-course-of-arbitrariness-makers of the world.

Re:I Won't Hire People Who Use Poor Grammar by jopt on Monday July 23, 2012 @03:36AM (#4279966)
You lost me at "it's".

Perhaps standard grammar is not, as you argue, the best measure of semantic correctness. Then please, let us violate standard grammar wherever it improves accuracy.

Writing something different from what you mean because the two sound alike does not qualify.

I'm fond of Bertrand Russell myself. Does your argument stand on its own?

Re:I Won't Hire People Who Use Poor Grammar by nessus42 on Monday July 23, 2012 @09:35AM (#4280852)
If we were to replaced both "it's" and "its" with just "its", absolutely no expressiveness in the language would be lost. This is shown by the fact that in spoken English, there is no audible distinction between these words. You can tell which word is being used 100% of the time that they are used in a sentence by the context alone. No sane person ever argues that we should introduce an audible distinction between "it's" and "its" in order to make a more expressive spoken language.

I don't know what Bertrand Russell would say, but I know what the great writer George Bernard Shaw would say. He lobbied very hard for a transition to a completely phonetic alphabet. I think he sometimes even wrote using it.

Re:I Won't Hire People Who Use Poor Grammar by jopt on Thursday July 26, 2012 @03:27PM (#4298085)
That's completely hypothetical. I could say "cat" and "dog" should in the future both be called "dog." That doesn't really excuse calling cats dogs.

Perhaps a new standard of spelling could be created and, as you suggest, "it's" and "its" could be replaced by "its." But that's not what you're doing when you write "it's" instead of "its;" instead, you are writing a word that is different from the one you mean.

"Its" has a meaning now, today, that whoever parses you language will use. Perhaps you will convince everyone to overload that meaning with a new one, but in the meantime write what you mean.

Re:I Won't Hire People Who Use Poor Grammar by nessus42 on Thursday July 26, 2012 @07:17PM (#4299214)
In the meantime, I'm dyslexic, and you don't seem to be very considerate of that.

Additionally, what I said is not hypothetical. It's a linguistic fact. Your comparison of phonetic spelling to replacing "cat" and "dog" with one word is a linguistic falsehood.

Perhaps someday falsehoods will be as accepted as facts, but in the meantime, speak the truth.

Re:I Won't Hire People Who Use Poor Grammar by jopt on Friday July 27, 2012 @10:52AM (#4301678)
Writing "pier" instead of "peer" is, just like writing "cat" instead of "dog," wiring something different from what you mean. Your reason for confusing "pier" and "peer" doesn't make them the same. Perhaps it's hard to get the right answer, but that doesn't make a wrong answer right.

As for your dyslexia, I don't think it's relevant. Your case for phonetic spelling wasn't specific to dyslexics.

Re:I Won't Hire People Who Use Poor Grammar by nessus42 on Friday July 27, 2012 @02:36PM (#4302901)
If "pier" and "peer" were merged into one word, then there would be sentences that are ambiguous. No such ambiguities arise with "its" vs "it's". They aren't even the same parts of speech.

You also have an incorrect notion of right and wrong. Read up on some linguistics and get back to me. E.g., there is nothing more "right" about "Standard Written English" than there is about the dialects spoken in inner cities. Both are equally good, full rich languages. Though certainly mistakes can be made within a dialect, you must understand, in order to be a civilized human, that for many native English speakers, their native language is not Standard Written English, but rather a regional dialect. Consequently, when they are in a situation where they are expected to communicate in Standard Written English, they are being expected to communicate in a language that is not their native language, and yet many people will not afford them the allowances that we make for people whom no dialect of English is their native language.

As for my dyslexia, it certainly is relevant, as this entire thread, from when I started posting on it, which is a direct ancestor of this post, and yours, is about whether it is moral to deny people jobs just because they make such an unimportant mistake. It's a mistake that never actually matters, except to the pedantic, and it's a mistake that dyslexics are particularly prone to. Not because they don't understand the difference, but rather because they often can't see when such mistakes are made.

Re:I Won't Hire People Who Use Poor Grammar by bguthrie on Friday July 20, 2012 @09:41AM (#4270701)
This is very much a cultural fit test. If people who use poor grammar are going to drive the author nuts, then as the the person running the company I think he's perfectly justified in treating the candidate as a poor cultural fit.

Additionally, as someone who employs writers as well as programmers, he might reasonably want to hire a programmer who is also a writer for the same reason that you'd want to hire a programmer who also has ops experience: it makes them a more appealing hire for the kinds of problems his startup is trying to solve.

In short, I don't see the problem.

Re:I Won't Hire People Who Use Poor Grammar by kamaal on Friday July 20, 2012 @10:43AM (#4271003)
>>In short, I don't see the problem.

You don't see the problem because you look at it from a different direction.

Hiring good programmers is already hard enough. And you are likely to hire a bad programmer despite having them run through many programming interview sessions.

If you put all sorts of irrelevant criteria in between, you are likely to get people who have mastered the art of beating interviews by specializing in those criteria and diverting your attention from actual issues. Then we all go back and complain why its so hard to hire 'good' programmers.

Ultimately you get what you truly want.

Re:I Won't Hire People Who Use Poor Grammar by bguthrie on Friday July 20, 2012 @11:56AM (#4271348)
I claim that the mathematics of hiring aren't all that different from the mathematics of beauty:

  http://blog.okcupid.com/index.php/the-mathematics-of-beauty/
The OP generated a lot of strong negative reactions. But it also generated some strong positive reactions from programmers who share the author's frustrations and would enjoy working at a place where everyone punctuates impeccably. Like the author, my experience has been that programmers who care about language tend to write beautiful code.

I'm not looking for a job. But if I was, this article would make me more, not less, likely to apply.

Re:I Won't Hire People Who Use Poor Grammar by knewter on Saturday July 21, 2012 @03:06AM (#4274211)
I'm an owner at a software dev shop now, and I loved this article. I can't imagine actually using grammar as a litmus test, personally, but it definitely goes into my on-the-spot judgement criteria. I feel significantly less-comfortable working with someone who lacks the critical thinking skills or personal professionalism to be intensely concerned with how they interact with others - and grammar is significantly about that.

If you can't be bothered to learn grammatical syntax, and it's something you've done your whole life, why should I expect that you'll be bothered to pursue perfection in other areas? If you are bothered to pursue it, why should I believe you have a chance at approaching it if you haven't nailed something you've done since you were five years old?

Anyway, I've not taken the time till now to really develop my understanding of this flash judgement I make of people, but it has always really bugged me. I have a friend who some people view as 'redneck' because he's got a bit of southern good-ol-boy in his heritage, but he's been reading books since he was young and it shows. We took a chance on him, brought him in-house, and trained him. One of the reasons I knew he'd become a great developer was because of the attention to detail he gave to everything that he did. It played out extremely well, for us and for him, and that one signal was a huge part of it.

Obviously anecdotal; typical caveats apply. Still, I'd rather live in the world iFixIt's pursuing than the world we presently live in, re: grammar.

EDIT: hilariously, for grammar. I missed a question mark.

Re:I Won't Hire People Who Use Poor Grammar by khwang on Friday July 20, 2012 @02:01PM (#4272054)
It's too bad you failed to use the subjunctive properly then. ;)
Re:I Won't Hire People Who Use Poor Grammar by mamoswined on Friday July 20, 2012 @12:54PM (#4271694)
as Tokenadult's comment points out, such "cultural fit" tests may be illegal http://news.ycombinator.com/item?id=4270768
Re:I Won't Hire People Who Use Poor Grammar by gergles on Friday July 20, 2012 @02:18PM (#4272150)
Writing skills are clearly a BFOQ for an organization where your entire work product is written; there is absolutely nothing illegal about a writing test for a programming job.
Re:I Won't Hire People Who Use Poor Grammar by dedward on Friday July 20, 2012 @09:33AM (#4270655)
It's not a sneak test - it's an actual grammar test. If you are asked to document something, and you can't observe basic english grammar, I see a problem too. Zero tolerance may be taking it a bit too far, but one would imagine he can tell the difference between a typo in a big test and actual fundamental lack of knowledge of the grammar you should have learned by the time you were 14.

(Yes, the double space after the period is a built in habit from typing class, and a debatable item in the computer age, but nobody seems to care one way or the other.)

Re:I Won't Hire People Who Use Poor Grammar by nollidge on Friday July 20, 2012 @10:08AM (#4270851)
> but nobody seems to care one way or the other.

Typographers do! Double-space is OK for monospace fonts, but otherwise single-space is almost universally preferred for avoiding so-called "rivers" of whitespace.

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

Re:I Won't Hire People Who Use Poor Grammar by einhverfr on Friday July 20, 2012 @11:04AM (#4271091)
Indeed. I'd point out that LaTeX does kerning independent of number of spaces after a period. I usually put two spaces when I type because I do a lot with monochrome fonts including all my LaTeX sources, but really, it is no substitute for proper kerning.
Re:I Won't Hire People Who Use Poor Grammar by blahedo on Friday July 20, 2012 @01:49PM (#4271979)
> I'd point out that LaTeX does kerning independent of number of spaces after a period.

This is misleading. Yes, LaTeX ignores how many spaces you put after the period in the source; but it does lay out extra space after sentence-ending characters. To avoid the extra space (e.g. if you have a mid-sentence abbreviation) you have to backslash it!

Re:I Won't Hire People Who Use Poor Grammar by irahul on Friday July 20, 2012 @09:44AM (#4270727)
> (Yes, the double space after the period is a built in habit from typing class, and a debatable item in the computer age, but nobody seems to care one way or the other.)

Well, it does serve a purpose in the computer age - grepping for sentence ending.

Re:I Won't Hire People Who Use Poor Grammar by FreebytesSector on Friday July 20, 2012 @10:05AM (#4270842)
Also, it makes it easier to determine when a sentence ends that contains an abbreviation. (This refers to when most people would use periods at the end of abbreviations.) I still use double spacing even though standard HTML does not display the double spacing on web pages.

The following sentences are an example of what I was saying:

"I sent the N.D.A. to N.Y.  It arrived three days later."

The single space after the "A" in "N.D.A." indicates that the sentence has not ended even though there is a period.

Re:I Won't Hire People Who Use Poor Grammar by einhverfr on Friday July 20, 2012 @11:36AM (#4271236)
Actually with a [A-Z]. [a-z] that's an easy case.

The harder case is an [A-Z]. [A-Z] which is not a sentence ending. Consider the following:

"When we compare the use of mistakes in speech in the Saga of St. Olaf with some of the other Old Norse literature, we can see that there is, in fact, a pattern of use of errors in speech being a sort of death omen."

The single space there identifies that there is no end of sentence between St. and Olaf. Of course when you are working in LaTeX you have to tell LaTeX that this is a word break and not a sentence break or else it will kern it as an end-of-sentence.

Re:I Won't Hire People Who Use Poor Grammar by pnathan on Friday July 20, 2012 @11:57AM (#4271354)
As a programmer - I can't stand working with coworkers who have lousy grammar and communication abilities. Most of my work either is communication, or will require communicating what I did to someone else, or communicating with someone else about what they did.

I can endure the relaxed grammar texts and IMs can use, but in practical & formal terms, I want decent writing and competent communication . I absolutely have zero interest in working with someone who has pathologically bad grammar & writing skills. We need to talk to each other, and grammar is a key component in unambiguous written communication.

Re:I Won't Hire People Who Use Poor Grammar by mamoswined on Friday July 20, 2012 @12:54PM (#4271688)
Me too. And it does affect their programming in some obvious ways. Particularly if you are working with English language-heavy languages like Javascript. But even if you aren't, comments that are absent or unreadable can make working with someone's code a nightmare. Forget about documentation. And I'll never forget having to work with some code where a variable was "pubic_key."
Re:I Won't Hire People Who Use Poor Grammar by Sunlis on Friday July 20, 2012 @09:30AM (#4270640)
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.
Re:I Won't Hire People Who Use Poor Grammar by irahul on Friday July 20, 2012 @09:37AM (#4270681)
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 50 push-ups.

The thing is, I don't see the correlation between grammar and the job I am supposed to do, but more importantly, by doing that, you aren't warranting me the respect I believe I deserve. I have a particular job and screening procedure in mind. If you ask me to skip rope, irrespective of my ability do so, I will have to deny.

Re:I Won't Hire People Who Use Poor Grammar by clarkevans on Friday July 20, 2012 @09:41AM (#4270706)
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 they think, and, well, how well they would document their software.

Re:I Won't Hire People Who Use Poor Grammar by irahul on Friday July 20, 2012 @09:50AM (#4270759)
> 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 by rys on Friday July 20, 2012 @10:39AM (#4270989)
So teach yourself not to make the mistakes because the next person in behind you working on your code might not know what you mean. If you know the difference it's just laziness to not communicate correctly.

As for periods outside of parentheses or not, that's syntax, not grammar. Your position here is weak. Good grammar is an indication that the person wielding the language at least takes care over what they're doing. A valuable trait for anyone, no matter what.

Re:I Won't Hire People Who Use Poor Grammar by irahul on Friday July 20, 2012 @04:12PM (#4272674)
> So teach yourself not to make the mistakes because the next person in behind you working on your code might not know what you mean.

For the nth time, I am not talking about "monkeys banging on keyboard" grammar.

> As for periods outside of parentheses or not, that's syntax, not grammar

Syntax is not grammar?

It isn't that hard to fact-check before confidently correcting someone.

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

> Good grammar is an indication that the person wielding the language at least takes care over what they're doing.

Good grammar is an indication of good grammar, and that's that. If you believe it's otherwise, well, your believes aren't fact. Please provide citations.

Re:I Won't Hire People Who Use Poor Grammar by keithpeter on Friday July 20, 2012 @11:45AM (#4271275)
"...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."

Does the company in the original post not recognise the function of an editor?

Re:I Won't Hire People Who Use Poor Grammar by terryk88a on Friday July 20, 2012 @11:48AM (#4271297)
Absolutely you do not have to subject yourself to his whims. You would be free to walk out the door if you found the grammar test offensive, or the push-ups test, or the rope-skipping test.

You do not deserve respect. Ever. You must always earn it.

Re:I Won't Hire People Who Use Poor Grammar by irahul on Friday July 20, 2012 @04:18PM (#4272704)
> Absolutely you do not have to subject yourself to his whims. You would be free to walk out the door if you found the grammar test offensive, or the push-ups test, or the rope-skipping test.

> You do not deserve respect. Ever. You must always earn it.

There are multiple types of respect. "One human being to another" is the basic type. Everyone deserves that. Another is earned. And the last one is context dependent.

If I am coming in for a programming job, there are expectations and norms. I come in and you ask me to unclog the toilet since you read in some blog about some CEO doing it or it represents loyalty or commitment or whatever the fuck, I am free to walk out and I will walk out. But that doesn't excuse the fact that you didn't warrant me the respect I deserved.

Re:I Won't Hire People Who Use Poor Grammar by Produce on Friday July 20, 2012 @12:03PM (#4271379)
Oh god. I hate this attitude. Respect is a right, not a privilege. Why should anyone have to earn something so basic? Do we also have to earn our privilege to breathe air? We're all equals and equally deserve respect. Yes, even you after you muttered that banality.
Re:I Won't Hire People Who Use Poor Grammar by angersock on Friday July 20, 2012 @02:46PM (#4272294)
Equals? Hardly. Some people, for example, are worse than others at English grammar--thus the OP.

What does respect mean to you, out of curiosity?

Re:I Won't Hire People Who Use Poor Grammar by Produce on Friday July 20, 2012 @03:26PM (#4272495)
I would say that we're definitely not identical, but we can all be equal.

A better question, though I will answer yours shortly, is what does equality mean? It's simply the relative value we assign something. The thing is, we can think in terms of valuable and not valuable or we can skip the duality altogether and see everything on an equal level. A spade is thoroughly unvaluable if you have no hole to dig yet indispensable when you do. So what is it's absolute value? Is it equal to a saw? Is one person equal to another? It all depends on your perspective.

The problem with seeing inequality between people in terms of respect is that you will treat some of your fellow man badly, since you don't respect them. If their value is merely a matter of perspective, which is ever changing, would it not make more sense to see past our biases and show everyone respect, whether they are equal to what we currently identify as respect worthy or not?

To me, respect means to consider someone in high regard. In my experience, how I look at people ends up affecting how they act. People always tend towards living up to the expectations placed on them. By showing someone that I don't respect them, I am pushing them down rather than helping them up.

Putting it another way, when someone is on the defensive, because someone else looks down on them and does not show them respect, they close up and are not receptive to new information. By showing them respect even if they are bad at something, they are likely to listen to what you have to say and change how they act as a result of your words. Disrespecting someone with - "you type like an idiot" or ignoring them, will make them respond appropriately. Validating their actions - "cool, a more condensed form of English!" then suggesting something else - "I've had lots of success finding a job by writing like this", they might actually change.

If we want society (and spelling) to improve, we have to embrace those we call idiots and teach them, not push them away.

If someone is an awesome programmer but can't write English to save his life, why not educate him? You'll certainly have a more loyal employee if he feels that he's gained important skills from you.

tl;dr - Disrespect is damaging, respect is nurturing. Respect everyone and the sun will shine brighter.

Re:I Won't Hire People Who Use Poor Grammar by derleth on Friday July 20, 2012 @02:32PM (#4272216)
> You do not deserve respect. Ever. You must always earn it.

Hm. If you don't have my respect, I may well feel justified in stealing from you. Is that really the kind of 'lack of respect' you think should be the default state?

Re:I Won't Hire People Who Use Poor Grammar by klawed on Friday July 20, 2012 @09:38AM (#4270685)
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?
Re:I Won't Hire People Who Use Poor Grammar by gawker on Friday July 20, 2012 @09:58AM (#4270809)
Watching how someone makes their bed shows their behaviour towards paying attention to detail. Even if they don't know how to do it, if someone chooses not to do or chooses to give up, it's clear sign that the person will probably not do something out of their domain.

If you're in a startup, you wear many hats. You do what it takes to succeed. If you have no clue how to do sales, find a way.

Re:I Won't Hire People Who Use Poor Grammar by Goronmon on Friday July 20, 2012 @11:44AM (#4271274)
>Watching how someone makes their bed shows their behaviour towards paying attention to detail. Even if they don't know how to do it, if someone chooses not to do or chooses to give up, it's clear sign that the person will probably not do something out of their domain.

I'm really not trying to be argumentative here, but this seems really silly. Replace "make a bed" with something like "kick a 40 yard field goal" or "craft a wooden chair" or more simply "tie a Windsor knot". All your testing is whether they care about that particular task that is in no way related to skills you actually need.

Re:I Won't Hire People Who Use Poor Grammar by gawker on Friday July 20, 2012 @02:13PM (#4272123)
Sure it might sound silly but sometimes it's not whether you can actually do the task or not. It's more of how will you approach something that you are not expected to do. Different people have different approaches.

I agree that if you're hiring a programmer strictly to program and do nothing else, that's fine. But if you're looking for someone who thinks outside of the box, is capable of coming with ideas and solutions when the solutions are yet to be known, having tests like these is probably a way to figure out how a person thinks. Whether it's a good way or not, I'm not so sure as I've never had to administer one of these tests.

Re:I Won't Hire People Who Use Poor Grammar by lotyrin on Friday July 20, 2012 @09:52AM (#4270771)
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 by klawed on Friday July 20, 2012 @10:00AM (#4270814)
The idea of using grammar as a litmus test for all new hires is akin to saying that nothing is more important than natural language grammar. That could not be further from the truth. I've read plenty of extremely thoughtful, info-dense specs in the open-source community that had typos and grammar errors. I've seen countless emails from colleagues that were clearly quickly written and thus contained errors. The essential ideas were none-the-less transmitted. My mind is able to auto-correct when needed. Perhaps if the rules of english grammar were based on logic and reason rather than the memorization of arbitrary, capricious rules I'd be willing to attach more wait to the grammar skills of non-professional writers.
Re:I Won't Hire People Who Use Poor Grammar by TeMPOraL on Friday July 20, 2012 @01:26PM (#4271865)
> I've read plenty of extremely thoughtful, info-dense specs in the open-source community that had typos and grammar errors. I've seen countless emails from colleagues that were clearly quickly written and thus contained errors. The essential ideas were none-the-less transmitted.

And because people tolerate it and allow for this to happen, we live in such ugly world, where people don't give a damn about quality.

Re:I Won't Hire People Who Use Poor Grammar by derleth on Friday July 20, 2012 @04:48PM (#4272822)
> where people don't give a damn about quality.

Similarly, nobody has fine tapestries on the walls of their server rooms. Nobody cares about the insulation properties, apparently, but worst of all, nobody cares about the attention to detail and quality a fine tapestry represents. Thus we live in a terrible world with no appreciation of the finer things, because if you don't mind the lack of tapestries, how can you possibly care about a lack of code quality?

Re:I Won't Hire People Who Use Poor Grammar by TeMPOraL on Saturday July 21, 2012 @04:17AM (#4274320)
Getting basic grammar poorly is not like having no tapestries on walls of server rooms. It's like having a big mess in server room, where machines lie around in unorderly fashion and cabling is a mess. Yes, it works. But it looks terrible. Also add unfinished pizzas laying on the floor for accurate representation of people who don't care about spelling.
Re:I Won't Hire People Who Use Poor Grammar by irahul on Friday July 20, 2012 @04:25PM (#4272741)
> If you're writing more code than natural language (documentation, discussion of specs, interaction with the team, etc) something is extremely wrong.

As long as we are just throwing claims around, I posit unless the code you write isn't 99% of what you write, something is extremely fucked up, and the orcs will take over the world.

I don't see how your claim is more valid or invalid than mine. None of the claims are backed by data, and personal perceptions are, well, personal. No one other than person experiencing it gives a damn.

Re:I Won't Hire People Who Use Poor Grammar by lotyrin on Friday July 20, 2012 @05:33PM (#4272998)
Perhaps, except that hypothetical code-hungry orcs are imaginary and have nothing to do with anything while the value of any of my very real examples is well understood by pretty much anyone. (Though - if you'll forgive me drawing further from our mystical beastiary - trolls might be an exception?)

Edit to explain why I'm so dismissive:

I think that it's a fairly accepted axiom that specified and documented projects are easier to maintain than the alternative. Likewise with code size versus feature set. I think it's self-evident that teams that communicate in natural language (even if only via a ticket system) are more functional (or at least more tolerable to be a member of) than teams that do not.

Deriving my claim from these seems reasonable enough, to me, given the context of the discussion (a comment thread of a relevant topic on some website a minority of people care about).

Not everything is science and while it might be nice to have 5-sigma data to reinforce my opinon, it fortunately doesn't need to be so reinforced in order to be valid, or even valid to be worth sharing.

Re:I Won't Hire People Who Use Poor Grammar by irahul on Friday July 20, 2012 @11:31PM (#4273847)
> Perhaps, except that hypothetical code-hungry orcs are imaginary and have nothing to do with anything while the value of any of my very real examples is well understood by pretty much anyone.

What does this even mean? I don't see any real examples, and all you are doing is throwing more claims around. I missed the memo where you, and whoever this "everyone" else is were appointed authority on the value of anything for everyone else.

> Edit to explain why I'm so dismissive: I think that it's a fairly accepted axiom that specified and documented projects are easier to maintain than the alternative.

So a project with beautiful documentation and totally retarded code is easier to maintain? Documentation, more often than not, is for the end user. As far as code maintenance goes, the most important factor is proper abstractions and encapsulations. If you wrote a 5000 line, well commented method, it doesn't help me at all.

And a very specific set of projects lead itself to and require beforehand specs. Majority of the real world runs on "code is spec". Where is the spec for linux? Here is a little unknown someone's views on specs http://kerneltrap.org/node/5725 Where are the specs for rails, sinatra, django, flask? And how would it help if suddenly a rails specs came into being? You are confusing your little well with the world. Most projects design interfaces, not specs(activerecord, rails 4 queuing api etc)

Even your axiom holds(it doesn't, at all), how does that imply if you're writing more code than natural language (documentation, discussion of specs, interaction with the team, etc) something is extremely wrong.?

> Deriving my claim from these seems reasonable enough, to me, given the context of the discussion

> Not everything is science and while it might be nice to have 5-sigma data to reinforce my opinon, it fortunately doesn't need to be so reinforced in order to be valid, or even valid to be worth sharing.

I didn't ask for 5-sigma data. I asked for data which isn't personal anecdotes and viewpoints presented as truth.

Re:I Won't Hire People Who Use Poor Grammar by klawed on Friday July 20, 2012 @09:33AM (#4270657)
>You must be fun to work with. A CEO whose litmus test to hir a programmer isn't programming finesse or cultural fit or drive..., but how good is his grammar.

Love the typo in your last line. Love it even more if it was unintentionl.

Re:I Won't Hire People Who Use Poor Grammar by devb on Friday July 20, 2012 @09:38AM (#4270687)
There are far too many typos and grammar errors in that post for its writer to be playing around. I think someone is bitter about their poor grasp of grammar constructs.
Re:I Won't Hire People Who Use Poor Grammar by warmwaffles on Friday July 20, 2012 @10:04AM (#4270832)
you, sir, just, do, not, grasp, simple, english, constructs.
Re:I Won't Hire People Who Use Poor Grammar by bane on Friday July 20, 2012 @09:31AM (#4270646)
good writing doesn't automatically come with proper grammar.

In fact I'd say good writing usually eschews many "rules" of proper grammar.

Re:I Won't Hire People Who Use Poor Grammar by nollidge on Friday July 20, 2012 @10:10AM (#4270860)
Sure, but typically it's deliberate on the part of the author.
Re:I Won't Hire People Who Use Poor Grammar by nirvdrum on Friday July 20, 2012 @11:09AM (#4271111)
Right. You should know the rules so you know when to break them. Stephen King hits on this point well in "On Writing." That book is a great read and takes a very non-parochial approach to writing.
Re:I Won't Hire People Who Use Poor Grammar by excuse-me on Friday July 20, 2012 @11:45AM (#4271276)
If you are Joyce you can get away with changing the rules - but nobody is going to read you anyway.

Similarly if you are Knuth you can talk about literate programming replacing C but nobody is going to hire you to do embedded development

Re:I Won't Hire People Who Use Poor Grammar by sopooneo on Friday July 20, 2012 @10:17AM (#4270888)
"Apart from my words, I have my intent, thoughts, opinions, facts. Words are a medium." But in written communication all those other things must be conveyed by your words. That's what writing is.
Re:I Won't Hire People Who Use Poor Grammar by irahul on Friday July 20, 2012 @04:32PM (#4272769)
> But in written communication all those other things must be conveyed by your words.

> That's what writing is.

So if I writing is just words, my grammatically correct words are as good as Orwell's, right? Writing isn't just about words - words are but a minor detail. Why did anyone read "A Clockwork Orange" when it butchered words in some very creative ways?

Do you have anything interesting to say, are you bringing anything new to the table, are you reporting facts, is this an opinion piece, and a thousand other things are what makes writing a powerful medium. How to use correct grammar is a very small variable in the scheme of things.

Re:I Won't Hire People Who Use Poor Grammar by snambi on Friday July 20, 2012 @01:45PM (#4271955)
I agree. Less words are better. Someone is looking for grammer to hire, may be he should move to publishing industry.