Only the hippest H1-B visa candidates need apply.

It's hard for some of us not to look at grammatical or spelling errors and wince.

Proofreading text isn't that different from proofreading code. Maybe it's part of the way geek brains are wired. Reading a paragraph and noticing that the author used "their" instead of "they're" might use a similar part of the brain that alarms you when you see a missing semicolon, or the wrong variable name, or "p++" instead of "++p," etc.

And when I see sloppy but functional code -- written by someone else, of course ;-) -- I instantly question the compentency of the coder, whether that's fair or not. Having the same reaction to poor grammar/spelling is understandable, since most of us have been reading English longer than we've been reading code.

Obviously, there are different levels of formality (in spoken as well as written English), but deliberate slang, jargon, abbreviations, etc. are different than errors (which are either accidental or a result of laziness or ignorance). Non-native speakers do get some slack, but their English is often better...