You're talking about completely different thing than what OP was talking about. It's about developer having a different vision than you. You either need to acc

You're talking about completely different thing than what OP was talking about. It's about developer having a different vision than you. You either need to accept that someone sees the problem differently than you and accept their solution, or if it is something important to you, you need to get better at explaining your vision. Anyway, back to your requirements, as you pointed those requirements are subjective. If those are important things you should still outline what's expected. You don't have to do it for every project, and can be when person is being on-boarded.