<?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: Designer vs Web Designer</title>
	<atom:link href="http://cameronyule.com/2008/05/designer-vs-web-designer/feed" rel="self" type="application/rss+xml" />
	<link>http://cameronyule.com/2008/05/designer-vs-web-designer</link>
	<description>Glasgow based new media developer Cameron Yule.</description>
	<lastBuildDate>Wed, 24 Feb 2010 18:59:02 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Paul</title>
		<link>http://cameronyule.com/2008/05/designer-vs-web-designer/comment-page-1#comment-20</link>
		<dc:creator>Paul</dc:creator>
		<pubDate>Tue, 20 May 2008 22:22:47 +0000</pubDate>
		<guid isPermaLink="false">http://cameronyule.com/?p=37#comment-20</guid>
		<description>Nice post Cam. 

I believe it is fair enough for designers to dabble in js/flash but when your separating languages to certain roles this must fall to the developer as the designer is likely to fall at the first hurdle.

It all depends on who is driving the ship and what sort of background they came from, design/ dev (if any). Maybe also on workload, if the company gets more dev work than they can handle it ultimately fall to the designers to handle the learning curve.

As for Andrew&#039;s previous employment, replace support-monkey, with super -monkey</description>
		<content:encoded><![CDATA[<p>Nice post Cam. </p>
<p>I believe it is fair enough for designers to dabble in js/flash but when your separating languages to certain roles this must fall to the developer as the designer is likely to fall at the first hurdle.</p>
<p>It all depends on who is driving the ship and what sort of background they came from, design/ dev (if any). Maybe also on workload, if the company gets more dev work than they can handle it ultimately fall to the designers to handle the learning curve.</p>
<p>As for Andrew&#8217;s previous employment, replace support-monkey, with super -monkey</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cameron</title>
		<link>http://cameronyule.com/2008/05/designer-vs-web-designer/comment-page-1#comment-19</link>
		<dc:creator>Cameron</dc:creator>
		<pubDate>Tue, 20 May 2008 08:37:49 +0000</pubDate>
		<guid isPermaLink="false">http://cameronyule.com/?p=37#comment-19</guid>
		<description>I&#039;d like to hope that the first two places you mention are in the minority, but somehow I&#039;ve got a feeling they&#039;re not. 

Solely doing HTML/CSS is a job position so limiting that I can&#039;t imagine any serious agency would be actively looking for just that individual skill - especially when you consider the number of people able to do the same but so much more besides (JS, Flash, Server-Side) …

Madness!</description>
		<content:encoded><![CDATA[<p>I&#8217;d like to hope that the first two places you mention are in the minority, but somehow I&#8217;ve got a feeling they&#8217;re not. </p>
<p>Solely doing HTML/CSS is a job position so limiting that I can&#8217;t imagine any serious agency would be actively looking for just that individual skill &#8211; especially when you consider the number of people able to do the same but so much more besides (JS, Flash, Server-Side) …</p>
<p>Madness!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://cameronyule.com/2008/05/designer-vs-web-designer/comment-page-1#comment-18</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Tue, 20 May 2008 08:22:28 +0000</pubDate>
		<guid isPermaLink="false">http://cameronyule.com/?p=37#comment-18</guid>
		<description>The first two places I worked had a slightly different (more common? More retarded?) approach.

1) Developer told the name of a company and what they sold
2) Developer creates design for said company
3) Developer makes templates for said designs
4) Developer integrates templates into homebrew CMS
5) Developer trains customer on CMS
6) Developer deals with support requests

Feel free to swap in Developer with Designer with Support-monkey!

Now though, I know people who are virtually 100% HTML/CSS, who are just taking baby steps into JavaScript and who haven&#039;t/won&#039;t touch server-side languages. Impressive!</description>
		<content:encoded><![CDATA[<p>The first two places I worked had a slightly different (more common? More retarded?) approach.</p>
<p>1) Developer told the name of a company and what they sold<br />
2) Developer creates design for said company<br />
3) Developer makes templates for said designs<br />
4) Developer integrates templates into homebrew CMS<br />
5) Developer trains customer on CMS<br />
6) Developer deals with support requests</p>
<p>Feel free to swap in Developer with Designer with Support-monkey!</p>
<p>Now though, I know people who are virtually 100% HTML/CSS, who are just taking baby steps into JavaScript and who haven&#8217;t/won&#8217;t touch server-side languages. Impressive!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
