Erik Ableson 2 minute read
April 5, 2008

Brazen Careerist obviously never worked as a developer

Via The Lone Sysadmin. :

Writing without typos is totally outdated » Brazen Careerist by Penelope Trunk Interesting rant. Personally, typos bother me a lot. Having them in your document distracts me from your point. Enough of them and I stop reading. Many other people are like me. Do you want to run the risk of me being the guy you submit your resume to?

I have to agree with Bob Plankers here - I admit that when I'm in a hurry typos can slip through but that I do work at trying to stamp them out. I think that those of us that have done any development understand that compilers do not forgive typos, and that the language parser in the heads of your readers is based on a certain rule-set and that when you break those rules, the parser is going to give you different (unpredictable) results. Every language has it's rules and ignoring them leads to failures of communication. While mistakes will happen it is worth spending a moment to proof-read your own work, and if you're high profile enough, an editor is not out of the question. My favorite typo in the article was from the paragraph : > I am extremely knowledgeable about grammar. I can parse any sentence. I can sign the preposition song in my sleep. So I feel fine telling you that there are great writers who don’t know grammar.

My first thought was "you're the author of the preposition song and are signing copies?" which then went to "oh, you're signing the preposition song for the deaf" to "Ooooohhhh - 'sing' the preposition song - that makes a lot more sense".