And there's nothing wrong with something being "not-DB" - there are things I advocate that are not-DB. Since this thread is about DB and not-DB, I think it is important to put things in the correct category.
The problem arises when there's a conflict in principles... One method says do A and the other says in the same situation to do almost the opposite... Something's gotta give...