Ask HN: Many-to-Many relation by default, is that a good strategy?
Defining entities and their relationships at the start of a project is difficult if the requirements keep changing frequently or are not defined (for example, in a startup setup).
So, in that case starting with Many-to-Many relationship for entities, and then optimising the relationship as things become clear is a good database design strategy?