<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Collaboration Tips for Designers Working with Developers</title>
	<atom:link href="http://sixrevisions.com/web_design/collaboration-tips-for-designers-working-with-developers/feed/" rel="self" type="application/rss+xml" />
	<link>http://sixrevisions.com/web_design/collaboration-tips-for-designers-working-with-developers/</link>
	<description></description>
	<lastBuildDate>Mon, 29 Apr 2013 08:43:38 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Adam</title>
		<link>http://sixrevisions.com/web_design/collaboration-tips-for-designers-working-with-developers/#comment-69838</link>
		<dc:creator>Adam</dc:creator>
		<pubDate>Sat, 26 Jun 2010 00:51:11 +0000</pubDate>
		<guid isPermaLink="false">http://sixrevisions.com/?p=2339#comment-69838</guid>
		<description>Candace, 

You bring some good points to the table, however, doing things the way they make sense in the code is not always a sign of a &quot;lazy developer&quot;, we are the one&#039;s that need to take your designs and turn them into code to be interpreted by a web browser. 

Visuals are not the only thing that matters, with the semantic web being pushed so heavily, code to content ratios, page size and performance, not to mention SEO, all of these also have a place within a beautiful, fast and efficient web page, and i think it&#039;s slightly naive to think that, while fundamental, design will always trump these other factors.

Your conclusion however was spot on, it is about communication from all parts of the team, each part voicing their concerns when they have them.

MTA and Patrick, i&#039;m sorry, but i completely disagree with you both on the subject of non-coding designers, having a designer with &quot;absolutely no interest in coding&quot; or that &quot;should not have to design to code limitations&quot; is absolutely insane. It&#039;s like having a painter that has no understanding of the different kind of canvases on which he/she paints, a designer should always understand the medium with which they are working, even if it is at the most basic level.

As quite a few people have already, the key is communication, nip problems in the bud before they become costly issues for you or your client.</description>
		<content:encoded><![CDATA[<p>Candace, </p>
<p>You bring some good points to the table, however, doing things the way they make sense in the code is not always a sign of a &#8220;lazy developer&#8221;, we are the one&#8217;s that need to take your designs and turn them into code to be interpreted by a web browser. </p>
<p>Visuals are not the only thing that matters, with the semantic web being pushed so heavily, code to content ratios, page size and performance, not to mention SEO, all of these also have a place within a beautiful, fast and efficient web page, and i think it&#8217;s slightly naive to think that, while fundamental, design will always trump these other factors.</p>
<p>Your conclusion however was spot on, it is about communication from all parts of the team, each part voicing their concerns when they have them.</p>
<p>MTA and Patrick, i&#8217;m sorry, but i completely disagree with you both on the subject of non-coding designers, having a designer with &#8220;absolutely no interest in coding&#8221; or that &#8220;should not have to design to code limitations&#8221; is absolutely insane. It&#8217;s like having a painter that has no understanding of the different kind of canvases on which he/she paints, a designer should always understand the medium with which they are working, even if it is at the most basic level.</p>
<p>As quite a few people have already, the key is communication, nip problems in the bud before they become costly issues for you or your client.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: javad pourhosaini</title>
		<link>http://sixrevisions.com/web_design/collaboration-tips-for-designers-working-with-developers/#comment-66628</link>
		<dc:creator>javad pourhosaini</dc:creator>
		<pubDate>Fri, 14 May 2010 10:57:21 +0000</pubDate>
		<guid isPermaLink="false">http://sixrevisions.com/?p=2339#comment-66628</guid>
		<description>thanks chris</description>
		<content:encoded><![CDATA[<p>thanks chris</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DB</title>
		<link>http://sixrevisions.com/web_design/collaboration-tips-for-designers-working-with-developers/#comment-58140</link>
		<dc:creator>DB</dc:creator>
		<pubDate>Fri, 12 Feb 2010 12:56:06 +0000</pubDate>
		<guid isPermaLink="false">http://sixrevisions.com/?p=2339#comment-58140</guid>
		<description>Thanks for this article. Good communication between designer and developer is essential!</description>
		<content:encoded><![CDATA[<p>Thanks for this article. Good communication between designer and developer is essential!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eko Setiawan</title>
		<link>http://sixrevisions.com/web_design/collaboration-tips-for-designers-working-with-developers/#comment-56897</link>
		<dc:creator>Eko Setiawan</dc:creator>
		<pubDate>Sun, 24 Jan 2010 00:58:50 +0000</pubDate>
		<guid isPermaLink="false">http://sixrevisions.com/?p=2339#comment-56897</guid>
		<description>On our team, we always start on research and find inspiration layout, then we build a mockup on photoshop.
Thanks, this great tips to improve our performance.</description>
		<content:encoded><![CDATA[<p>On our team, we always start on research and find inspiration layout, then we build a mockup on photoshop.<br />
Thanks, this great tips to improve our performance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick</title>
		<link>http://sixrevisions.com/web_design/collaboration-tips-for-designers-working-with-developers/#comment-56484</link>
		<dc:creator>Patrick</dc:creator>
		<pubDate>Sat, 16 Jan 2010 13:16:14 +0000</pubDate>
		<guid isPermaLink="false">http://sixrevisions.com/?p=2339#comment-56484</guid>
		<description>MTA...amen!
I am a graphic designer. I have absolutely no interest in coding. Thats why I use a developer.
Good designers have a purpose (visually) for everything they do.
I have to keep reminding my coder that just dropping this or adding that changes the whole design.
that said, I have not designed anything that my developer couldnt implement.</description>
		<content:encoded><![CDATA[<p>MTA&#8230;amen!<br />
I am a graphic designer. I have absolutely no interest in coding. Thats why I use a developer.<br />
Good designers have a purpose (visually) for everything they do.<br />
I have to keep reminding my coder that just dropping this or adding that changes the whole design.<br />
that said, I have not designed anything that my developer couldnt implement.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott</title>
		<link>http://sixrevisions.com/web_design/collaboration-tips-for-designers-working-with-developers/#comment-56438</link>
		<dc:creator>Scott</dc:creator>
		<pubDate>Fri, 15 Jan 2010 04:27:41 +0000</pubDate>
		<guid isPermaLink="false">http://sixrevisions.com/?p=2339#comment-56438</guid>
		<description>great post thanks, its always a challenge working with a team</description>
		<content:encoded><![CDATA[<p>great post thanks, its always a challenge working with a team</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: titos2k</title>
		<link>http://sixrevisions.com/web_design/collaboration-tips-for-designers-working-with-developers/#comment-56385</link>
		<dc:creator>titos2k</dc:creator>
		<pubDate>Thu, 14 Jan 2010 11:24:01 +0000</pubDate>
		<guid isPermaLink="false">http://sixrevisions.com/?p=2339#comment-56385</guid>
		<description>I think that every webdesigner should know more and less the secrets of HTML, CSS and even JS/JQuery and make complete static web page, that developer will take care of by creating or adapting existing CMS env.</description>
		<content:encoded><![CDATA[<p>I think that every webdesigner should know more and less the secrets of HTML, CSS and even JS/JQuery and make complete static web page, that developer will take care of by creating or adapting existing CMS env.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MTA</title>
		<link>http://sixrevisions.com/web_design/collaboration-tips-for-designers-working-with-developers/#comment-56228</link>
		<dc:creator>MTA</dc:creator>
		<pubDate>Tue, 12 Jan 2010 04:20:36 +0000</pubDate>
		<guid isPermaLink="false">http://sixrevisions.com/?p=2339#comment-56228</guid>
		<description>I believe Candace highlights some good points for all parties to consider. In my experience, I could count on one hand the amount of people who are both competent designers and developers. Many think they can do both of course, but it&#039;s very rarely the case. In summary;
Good Designers should not have to design to code limitations (or lack of developer ability/technical contraints) and lets face it, practically anything can be built these days. So if your developer can&#039;t code the designers creative - get a new developer. Conversely, if your Designer can&#039;t listen to, work with and respect your Developer, get a new Designer. But the key is to remember -let the coders code, and the designers design.</description>
		<content:encoded><![CDATA[<p>I believe Candace highlights some good points for all parties to consider. In my experience, I could count on one hand the amount of people who are both competent designers and developers. Many think they can do both of course, but it&#8217;s very rarely the case. In summary;<br />
Good Designers should not have to design to code limitations (or lack of developer ability/technical contraints) and lets face it, practically anything can be built these days. So if your developer can&#8217;t code the designers creative &#8211; get a new developer. Conversely, if your Designer can&#8217;t listen to, work with and respect your Developer, get a new Designer. But the key is to remember -let the coders code, and the designers design.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Angela Bowman</title>
		<link>http://sixrevisions.com/web_design/collaboration-tips-for-designers-working-with-developers/#comment-56039</link>
		<dc:creator>Angela Bowman</dc:creator>
		<pubDate>Sun, 10 Jan 2010 03:43:20 +0000</pubDate>
		<guid isPermaLink="false">http://sixrevisions.com/?p=2339#comment-56039</guid>
		<description>Great article! I work with many print designers who have become web designers. Would be great to have a print design vs CSS design comparison, so designers would have a better sense of how to design for web and what CSS can and can&#039;t do and what types of layouts are better for CMS environments, etc.</description>
		<content:encoded><![CDATA[<p>Great article! I work with many print designers who have become web designers. Would be great to have a print design vs CSS design comparison, so designers would have a better sense of how to design for web and what CSS can and can&#8217;t do and what types of layouts are better for CMS environments, etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Forrest</title>
		<link>http://sixrevisions.com/web_design/collaboration-tips-for-designers-working-with-developers/#comment-56027</link>
		<dc:creator>Forrest</dc:creator>
		<pubDate>Sat, 09 Jan 2010 20:07:01 +0000</pubDate>
		<guid isPermaLink="false">http://sixrevisions.com/?p=2339#comment-56027</guid>
		<description>Thanks for the article.  I have for the first time been working with a coder (I think &#039;developer&#039; is misused in the computer world...but that&#039;s another topic) instead of doing everything on my own, and it has definitely been a learning process.  I got a few tips from this that should help.</description>
		<content:encoded><![CDATA[<p>Thanks for the article.  I have for the first time been working with a coder (I think &#8216;developer&#8217; is misused in the computer world&#8230;but that&#8217;s another topic) instead of doing everything on my own, and it has definitely been a learning process.  I got a few tips from this that should help.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
