I haven't really had this problem (I'm a developer) because I used to try to do some form of UX design way back in the day. And the more I did it, the more I re

I haven't really had this problem (I'm a developer) because I used to try to do some form of UX design way back in the day. And the more I did it, the more I realized I suck at it. So I can empathize with their needs and truly appreciate someone who can do it well. My recommendation would be to have those with a problem do the other person's job for a week and "sorta" hold them accountable for the outcomes. Give them the mere threat of some minor wrist-slap should they fail to meet a seemingly reasonable objective that the other could do in a week, and then after the exercise explain that you never had any intention of actually delivering on that - in this case - just to make them have some skin in the game so they didn't dismiss the exercise. After about a week of the shoe being on the other foot, I think the appreciation for the other discipline will become genuine, and then you can start working on having the right conversations about tooling, concerns, workflow, language, and so on. But developers have got to understand that UX design is so, so much more than "pretty pictures" and UX folks have gotta get it through their heads that engineering is FUCKING HARD, and we're way more than mere "code monkeys" over here. Until that mutual respect and appreciation is established, none of the other stuff matters.