<?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: Growing as a Designer &#8211; 10 Things I&#8217;ve Learned</title>
	<atom:link href="http://www.bluedaring.com/growing-as-a-designer-10-things-ive-learned/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bluedaring.com/growing-as-a-designer-10-things-ive-learned/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=growing-as-a-designer-10-things-ive-learned</link>
	<description>Blue Daring</description>
	<lastBuildDate>Thu, 25 Aug 2011 18:28:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Bryan</title>
		<link>http://www.bluedaring.com/growing-as-a-designer-10-things-ive-learned/comment-page-1/#comment-2669</link>
		<dc:creator>Bryan</dc:creator>
		<pubDate>Mon, 24 May 2010 15:49:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.bluedaring.com/?p=964#comment-2669</guid>
		<description>I agree with all your points on what makes a good designer, and would like to add one more.

Speaking as a web developer, a designer who knows his/her way around a little web-speak is invaluable. I suppose this could be said of any medium that you are working in, that there are technological implications that a designer should always be aware of.

As a print designer, you need to know how a printing process works so you have an understanding of what happens after you hand off your files. As a web designer, knowing how your design transforms into code can make the transition much easier on both sides.</description>
		<content:encoded><![CDATA[<p>I agree with all your points on what makes a good designer, and would like to add one more.</p>
<p>Speaking as a web developer, a designer who knows his/her way around a little web-speak is invaluable. I suppose this could be said of any medium that you are working in, that there are technological implications that a designer should always be aware of.</p>
<p>As a print designer, you need to know how a printing process works so you have an understanding of what happens after you hand off your files. As a web designer, knowing how your design transforms into code can make the transition much easier on both sides.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

