<?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: Designers vs Developers</title>
	<atom:link href="http://www.simonrjones.net/2010/05/designers-vs-developers/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.simonrjones.net/2010/05/designers-vs-developers/</link>
	<description></description>
	<lastBuildDate>Wed, 18 May 2011 03:12:10 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Steve O</title>
		<link>http://www.simonrjones.net/2010/05/designers-vs-developers/comment-page-1/#comment-28</link>
		<dc:creator>Steve O</dc:creator>
		<pubDate>Mon, 03 May 2010 18:02:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.simonrjones.net/?p=161#comment-28</guid>
		<description>Good point Simon, although I am guilty of designing in Photoshop until the client agrees to the design and only then switching to the browser. I keep it clear in my head what I can get away with in the browser and let the client know there may be small changes and I&#039;ve had no problems yet, but I know I should be doing more browser side first. Blame my print background!

We couldn&#039;t actually disagree with the question, “Designers who don’t understand technology can’t design for the web”. It is a whole other area of understanding and some print trained designers just don&#039;t see that. As such the client ends up with a poorly produced site. I saw a site designed by a copywriter a few weeks ago - great copy, bloody awful site.</description>
		<content:encoded><![CDATA[<p>Good point Simon, although I am guilty of designing in Photoshop until the client agrees to the design and only then switching to the browser. I keep it clear in my head what I can get away with in the browser and let the client know there may be small changes and I&#8217;ve had no problems yet, but I know I should be doing more browser side first. Blame my print background!</p>
<p>We couldn&#8217;t actually disagree with the question, “Designers who don’t understand technology can’t design for the web”. It is a whole other area of understanding and some print trained designers just don&#8217;t see that. As such the client ends up with a poorly produced site. I saw a site designed by a copywriter a few weeks ago &#8211; great copy, bloody awful site.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon R Jones</title>
		<link>http://www.simonrjones.net/2010/05/designers-vs-developers/comment-page-1/#comment-26</link>
		<dc:creator>Simon R Jones</dc:creator>
		<pubDate>Mon, 03 May 2010 06:54:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.simonrjones.net/?p=161#comment-26</guid>
		<description>Ah yes, that&#039;s automatic formatting in WordPress for you. I read this old article on EM dashes and other characters at ALA recently - http://www.alistapart.com/articles/emen/</description>
		<content:encoded><![CDATA[<p>Ah yes, that&#8217;s automatic formatting in WordPress for you. I read this old article on EM dashes and other characters at ALA recently &#8211; <a href="http://www.alistapart.com/articles/emen/" rel="nofollow">http://www.alistapart.com/articles/emen/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob Chant</title>
		<link>http://www.simonrjones.net/2010/05/designers-vs-developers/comment-page-1/#comment-25</link>
		<dc:creator>Rob Chant</dc:creator>
		<pubDate>Sun, 02 May 2010 22:33:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.simonrjones.net/?p=161#comment-25</guid>
		<description>(And just to be cheeky and extreme pedantic, from a designer&#039;s point of view, I notice your comment system automatically converts en-dashes to em-dashes. That&#039;s great, although a em-dash should have i-spaces to either side, not full spaces, of if i-spaces are unavailable, no spaces at all. They&#039;re also usually only used with serif typefaces, but that&#039;s just a matter of taste...)</description>
		<content:encoded><![CDATA[<p>(And just to be cheeky and extreme pedantic, from a designer&#8217;s point of view, I notice your comment system automatically converts en-dashes to em-dashes. That&#8217;s great, although a em-dash should have i-spaces to either side, not full spaces, of if i-spaces are unavailable, no spaces at all. They&#8217;re also usually only used with serif typefaces, but that&#8217;s just a matter of taste&#8230;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob Chant</title>
		<link>http://www.simonrjones.net/2010/05/designers-vs-developers/comment-page-1/#comment-24</link>
		<dc:creator>Rob Chant</dc:creator>
		<pubDate>Sun, 02 May 2010 22:30:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.simonrjones.net/?p=161#comment-24</guid>
		<description>Good point about designing in the browser -- I should have stuck my hand up and said this too! I don&#039;t think I&#039;ve ever once (or, at least, for many, many moons) designed a site in flat files and then got stuck into the mark-up. I always do everything straight in HTML/CSS. Obvious benefits are:

a) It&#039;s much quicker.
b) Your working with the actual destination system (rather than against it or in ignorance to it).</description>
		<content:encoded><![CDATA[<p>Good point about designing in the browser &#8212; I should have stuck my hand up and said this too! I don&#8217;t think I&#8217;ve ever once (or, at least, for many, many moons) designed a site in flat files and then got stuck into the mark-up. I always do everything straight in HTML/CSS. Obvious benefits are:</p>
<p>a) It&#8217;s much quicker.<br />
b) Your working with the actual destination system (rather than against it or in ignorance to it).</p>
]]></content:encoded>
	</item>
</channel>
</rss>

