Monday, July 30, 2012

Quotation Of The Day: Grammar Edition

From this Kyle Wiens post in Harvard Business Review:
On the face of it, my zero tolerance approach to grammar errors might seem a little unfair. After all, grammar has nothing to do with job performance, or creativity, or intelligence, right?
Wrong. 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. So, even in this hyper-competitive market, I will pass on a great programmer who cannot write.
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.
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. You see, at its core, code is prose. Great programmers are more than just code monkeys; according to Stanford programming legend Donald Knuth they are "essayists who work with traditional aesthetic and literary forms." The point: programming should be easily understood by real human beings — not just computers.
And just like good writing and good grammar, when it comes to programming, the devil's in the details. In fact, when it comes to my whole business, details are everything.
I have three quick reactions.  First, I need to proofread more carefully before I hit publish. Second, I have told students that a link exists between programming and grammar.  It's good to see someone support that premise. Finally, grammar is necessary but people who write with good grammar may still produce boring work: feel free to insert a necessary not sufficient cliche.

HT: Andrew Sullivan

No comments: