<?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: web developer vs web designer</title>
	<atom:link href="http://paulmcewan.com/index.php/2010/02/23/web-developer-vs-web-designer/feed/" rel="self" type="application/rss+xml" />
	<link>http://paulmcewan.com/index.php/2010/02/23/web-developer-vs-web-designer/</link>
	<description>A street level view with curb appeal</description>
	<lastBuildDate>Wed, 25 Aug 2010 03:45:01 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Murray Pearson</title>
		<link>http://paulmcewan.com/index.php/2010/02/23/web-developer-vs-web-designer/comment-page-1/#comment-732</link>
		<dc:creator>Murray Pearson</dc:creator>
		<pubDate>Fri, 25 Jun 2010 00:19:16 +0000</pubDate>
		<guid isPermaLink="false">http://paulmcewan.com/?p=452#comment-732</guid>
		<description>This is a good description, and good advice.

Not only is it unrealistic to expect a typical designer to be a good programmer, it&#039;s usually not a good idea even if you happen to find the rare individual with a grasp of both. (I know both areas well; for me, learning design, printing and programming has been a 25-year process!) Why&#039;s this?

Because any website with any significant complexity has many, many pieces. It&#039;s much more efficient to split up the load in a team and let people specialize their thinking / working processes, they can work smoothly and with fewer &#039;context switches&#039;: the process of mentally changing gears to cope with a greatly different task.

In a one-person show, all of the context switches happen to the same individual; they are alone in a project, which is isolating and demoralizing no matter how cool the project; and they have a whole lot of work to do without the prospect of relief. These factors are additive and the net drag is enough to stall many projects.

The solution: have one or more developers, and one or more designers. No less.</description>
		<content:encoded><![CDATA[<p>This is a good description, and good advice.</p>
<p>Not only is it unrealistic to expect a typical designer to be a good programmer, it&#8217;s usually not a good idea even if you happen to find the rare individual with a grasp of both. (I know both areas well; for me, learning design, printing and programming has been a 25-year process!) Why&#8217;s this?</p>
<p>Because any website with any significant complexity has many, many pieces. It&#8217;s much more efficient to split up the load in a team and let people specialize their thinking / working processes, they can work smoothly and with fewer &#8216;context switches&#8217;: the process of mentally changing gears to cope with a greatly different task.</p>
<p>In a one-person show, all of the context switches happen to the same individual; they are alone in a project, which is isolating and demoralizing no matter how cool the project; and they have a whole lot of work to do without the prospect of relief. These factors are additive and the net drag is enough to stall many projects.</p>
<p>The solution: have one or more developers, and one or more designers. No less.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
