Without reading the underlying links, I would guess at issue is the classic conflict between .net/java/whatever developers and database architechs/developers/dbas. Like many others on this forum, I have seen both sides and can understand the "whatever" developers desire to do what they want, to just use the database as a more permanent datastore. However, as you've pointed out, the rules/guidelines/best practices are there for a reason and the events revealed the gross lack of understanding/experience/(fill in blank here) of the architects.
The follow up question, as I am responding off the top of my head, are those really 2 separate issues?
1. Don't know or want to know the best practices for handling data and why DB architecture (schema and code for ACID-ity) is important.
2. Don't have the experience with these kinds of systems and the forethought to consider the soundness of the code, not just that it completes the drawn-up workflow diagram, and test for possible security issues.