While I mostly agree with the sentiment expressed in the editorial, there is one place where I don't. Where, in fact, I'd even reverse the statement:

"There really is little justification for not having a case-sensitive collation for database on a dev server"

When developing code, you can never be entirely sure what server(s) it will be deployed on. One of them could be neglecting Phil's good advice and using a case sensitive collation. And surely, you would not want your deployment fail because users get bucketloads of "Table cUstOMer not found" errors, because the table is acutally called "CusTOmeR".

Make sure you always develop and test on a case-sensitive server, and you'll never have these problems.

(And an added benefit is that you don't get the confusion sometimes caused by using different case for the same object in the same query).