It could become clear if you read through the article here: Choose a single layer of cleverness (Loud Thinking) - yes, exactly, his opinion is, out with referential integrity, stored procedures, and triggers from the database, because he wants to keep them all in his code. How about "throwing out the baby with the bathwater"?
It's so embarrassing that I almost don't know whether I should laugh about it - but one thing I certainly won't do: put my money on such a horse ...
Casual approaches with simple, clever solutions that sometimes go against conventions are okay (and important - otherwise we would all end up with Java and J2EE ...) - but if programming consists only of patching together half-baked solutions, then I'd rather stay out of it. I might as well use PHP then ...