You're right. Every discussion about "designers should code" always shows problem in teamwork and communication, not in coding skills. :)
And even if as I was saying learning to code is a way to create these skills, like designing things is for developers, another way is just listening to the developers/designers in your team. It works very well and it's way more efficient for a lot of different people. :)
Agreed, although "just listening" doesn't go as far as "just listening while also having walked a bit in their shoes, or at least tried those shoes on for size."
Comments
You're right. Every discussion about "designers should code" always shows problem in teamwork and communication, not in coding skills. :)
And even if as I was saying learning to code is a way to create these skills, like designing things is for developers, another way is just listening to the developers/designers in your team. It works very well and it's way more efficient for a lot of different people. :)
Teamwork, and trust.
Agreed, although "just listening" doesn't go as far as "just listening while also having walked a bit in their shoes, or at least tried those shoes on for size."
I saw a presentation by a designer/developer team a couple years back - one blog entry on that is here: http://www.viget.com/inspire/stop-driving-your-developers-cr...
Another here: http://www.viget.com/extend/stop-pissing-off-your-designers/
And slides here http://www.slideshare.net/mindywagner/10-things-designers-do...
Yeah, that's a huge collection of communication problems, great. Exactly on spot. :)