I'm going to throw my hat into the ring with Courtney on this one. I think the article misrepresents developers, at least good developers.

"I actually see the purpose of an ORM to provide compile-time checks against tables, queries etc. used. And providing easy and fast inserting, updating, querying entities are a lot easier via an ORM than cutting your own ADO style layer. Especially if you use LLBLGen rather than NHibernate or Entity Framework."

I'm happy enough with EF personally but agree with what Courtney says about the purpose of an ORM. I'll go further and say it helps to minimise the amount of explicit (i.e. non-constrained) business logic in a database. I'm happy in either DB or code realms and there is no doubt in my mind that code can generally be better structured outside of the database. Of course there is a time for SQL but eliminating some of the unpleasant monolithic code in procs and twisted nonsense I have found in views is no bad objective.

I do have developers who are less comfortable in SQL but that is where I (or several others) can step in. I've never heard of or wished for the elimination of SQL altogether, just desired to make it manageable.