Personally, I'd rather they didn't, and asked people who do to write them the DB objects they need. In my experience, it's the people who know a little about databases that are the most dangerous. (Heard from a senior C# developer: "You have to put the NOT NULL check first in the where clause" :ermm: )

The article's talking about LINQ and Entity Framework. I've looked into them a bit from the developer side. If they're implemented properly, they won't cause problems. The big issue I see is that all the examples that MS have published, show it been implemented the 'wrong' way.