[jggube]

>> "It’s our job to help translate their vision to the development team in a way that they can understand and accept."

>> "Similarly, we need to speak on behalf the developers to help reign in the designers, at times. If they are coming up with concepts that will be extremely difficult or time consuming to implement, we can explain the limitations of the technology and the complexity involved in implementing their designs"

I dislike this stereotype that developers can't communicate and work side-by-side with designers, and vice versa. It seems the writer thinks developers can't communicate or speak and need someone to translate for them, like they're a machine. It's quite disparaging, actually.

I also see a danger in having a middleman, so to speak. Things can get lost in translation.

[Goladus]

I'd say if your organization is large enough to differentiate between "UX Developer," "Traditional Developer," and "Designer" then yes there are going to be communication problems. It shouldn't be disparaging to either side.

Also it doesn't have to be a middle-man. 3-way communication usually works fine.