It is really arguing the extremes, when reality, the best place to be is somewhere in between.
Designers and developers should of course have good understanding and empathy for what the other person does. But at the same time, they shouldn't have such a complete understanding that it negatively impacts their primary role.
For example, if you're a designer, you don't want to fall into the trap of only incorporating things into your design that you already know how to code. You might leave a lot of innovative stuff out that would make the product better. If you're a developer, you don't always want to be bound by the existing design constraints either. It's a back and forth discussion between the two halves.
Comments
It is really arguing the extremes, when reality, the best place to be is somewhere in between.
Designers and developers should of course have good understanding and empathy for what the other person does. But at the same time, they shouldn't have such a complete understanding that it negatively impacts their primary role.
For example, if you're a designer, you don't want to fall into the trap of only incorporating things into your design that you already know how to code. You might leave a lot of innovative stuff out that would make the product better. If you're a developer, you don't always want to be bound by the existing design constraints either. It's a back and forth discussion between the two halves.