I would more suggest modelling what you want, and defaulting to 1:n if you aren't sure but not always using 1:n
There are many cases where its important things are 1:1.
I think the core impulse is to consider 1:n as an extension of 1:1. I think that is backwards. 1:1 is an extended version of 1:n with a specific restriction n=1. Often this restriction is critically important to the app. When you need 1:1 you should use it. If you don't know, use the generic 1:n form.
Agree -- 1:n is the safest approach if you don't know, but 1:1 has its place.
I think the core thing I've learned over time (in a startup) is that I rarely actually know for sure if there should be more of something, and 1:1 tends to create more "permanent" or "hard to reverse" changes to the way you design your system.
There are many cases where its important things are 1:1.
I think the core impulse is to consider 1:n as an extension of 1:1. I think that is backwards. 1:1 is an extended version of 1:n with a specific restriction n=1. Often this restriction is critically important to the app. When you need 1:1 you should use it. If you don't know, use the generic 1:n form.
P.s. weirdest clickbait headline ever.