I'd be curious to see some examples of what you mean! I think there are definitely cases where DB needs to compensate for bad architecture, but then even compe

I'd be curious to see some examples of what you mean! I think there are definitely cases where DB needs to compensate for bad architecture, but then even competent developers can profit from the flexibility of being able to ad new features ad hoc to an existing db schema/architecture and the DB just magically bailing them out.