News for hackers. Stuff that matters.
Re:Designer Eats Engineer by rglover on Sunday January 13, 2013 @09:28PM (#5052981)
Why does a designer who can code scare you? It's a good thing. I'm a designer that works in code and it often makes my relationship with devs a lot smoother. I understand limitations, can reduce dev time significantly, and together, we share strengths producing a wonderful interface.

The design then pass off flow sucks. It puts too much emphasis on ornament and not enough on functionality. As a designer, understanding how it's implemented and why improves your work significantly.

Re:Designer Eats Engineer by pixie_ on Sunday January 13, 2013 @10:15PM (#5053106)
It's not a 'good thing' to deal with piles of legacy spaghetti code with no method to it's madness. Sure if you've been coding UIs for years, I'm sure we'd work fine together. In my experience, coding designers, have not been experienced coders.
Re:Designer Eats Engineer by rglover on Sunday January 13, 2013 @10:37PM (#5053161)
I'm not sure what your relationship or proximity to these designers is, but the best thing you can do to cure this is educate. It can be frustrating, sure, but making an effort to teach and explain what's wrong can make all the difference.

Just because someone isn't top of the line doesn't mean they should be dismissed or frowned upon.

Further, if it's something mission critical, just politely ask them if you can work on it to ensure its quality.