Developers may not be visual thinkers. Still, the responsibility is on them to translate a layout accurately- or the designer’s time spent carefully considering each decision will be lost. I would encourage them to learn the basics of typography and research UI continuously, but mostly to measure, compare and look for proportions & alignments in the served designs. Most importantly, get on the same page with your designer about the variables you know will affect layout. What stretches? What aligns? What is fixed, and why? Request a markup of this information, yes, but don’t use it to replace a conversation.

Designers must consider the feasibility of the design just as they do the user experience, even if that means shooting for the stars first and bring it back to doable later. The best way for designers to do this is through an understanding, if not a skill, of front-end development. Go learn your web standards my friends, and talk to your developers with some concrete knowledge of code. If you want to be an industry leader, that’s what you must do. Also, try not to be too stubborn about layout. A good UI designer knows that the web is not print, even in the world of CSS.

Developers usually don’t have a very good eye for design, and who can blame them? It’s not their job, and I don’t think most designers would be very good at programming either.

That being said, I agree with Andrew Woods. Learning a bit about design if you are a developer, or the other way around is something that definitely helps communication.

Whenever I present a design to a developer I also try to explain why I designed it that way and hopefully in that process actually teach them some design. I think the opposite could work as well. Our developers as best as they can often try to explain data structures of our projects to me and it’s very helpful for me to understand what I’m working with.

[...] Original post: Communication Between Designers and Developers from a Developer’s View – Inspect Element [...]

On the other hand ive worked with 100% designers and i do get a bit jumpy at some requests as if a layout can be moved around like a vector in illustrator without making me make changes all over the sites code

‘Devine’ meaning developer and designer at the same time.
That generation will be at a whole new level.

If they’re not good at or don’t like one part, they’ll at least know what it’s about.

The way to bridge this divide is with knowledge and communication. Work with your colleagues to learn about their world. I’ve done this, and it’s made me a better developer for it. If your a designer, ask your developers for books and tutorials about OOP, PHP, and software design patterns. If your a developer, you should look into typography, css grids, accessibility, and UX. Having each side, learn the other’s lexicon will go a long way towards better communication and ultimately building better websites.