fname lname-1111520 (4/14/2011)
Craig Farrell (4/14/2011)
fname lname-1111520 (4/13/2011)
I get it: "then", "than", "there's", "there are". Stop reading (and I did), it can't be coherent.
Huh? Could you specifically quote where you found this incoherent for those reasons? I fear you've confused the heck out of me here.
Edit: even stranger, that post was at 10:38 PM before the article released. wha?
I'm sorry to say there isn't a big enough facepalm emoticon for the current state of job advertising in our industry. You're competing with employers looking for the most bang for their buck, HR firms/departments who know as much about tech as most techies know about oil rig equipment, local laws regarding job duty requirements, Visa (not the credit card) Renewal laws, and consulting/hiring firms who know more buzzwords then technology. They've had more practice at this then you probably have, and it can be difficult figuring out what's good and what's not.
Let's review a concept I brought up in my previous article before we get started. For SQL Server, there's 5
"then" and "there's"... I didn't find it incoherent. I claimed "it can't be coherent". If I were reviewing resumes, you go in the Engrish pile.
If you're looking for a translator, a teacher, an editor or a proofreader, demanding perfect English in a resume is probably sensible. This article, however, is about DBAs, and I've met plenty of database professionals with fantastic attention to detail and appalling English. If you focus on side issues, you will, sooner or later, overlook something both relevant and important. And if you rejected this article on the strength of those two mistakes, you shouldn't be in a position of evaluating resumes.
Semper in excretia, sumus solum profundum variat