4 ms·

When I'm working with a colleague who has a specialty, I don't generally concern myself with whether they're "my equal" but rather, whether they bring something

When I'm working with a colleague who has a specialty, I don't generally concern myself with whether they're "my equal" but rather, whether they bring something constructive to the table, in their specialty. I find "graphic designers" to be enormously helpful in solving problems related to user interaction and judgment with regard to use of color, typeface, and effective use of limited screen real-estate. There are good ones and bad ones. The key is to assess where they are, and learn how to communicate with them with regards to any technical impacts. The last thing I'd want to do in collaborating with a team-mate is summarily judge them as "my inferior". But that's (unfortunately) just me.

chii 5y ago
> summarily judge them as "my inferior" most organizations that tend to have office politics and are very politically-correct in their behaviour tends to end up with people in roles calling shots, despite those shots not being great. graphics designers is just one example of this that i've seen, where a poor UI or bad UX is mocked up, but because you're an engineer, you do not get to have much input or your input is regarded as irrelevant (because your role is to code, not do UX design). That's what i mean by the "inferior" comment - that the UX/UI designer isn't as good at their craft as you are in implementing code.