<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: How we picked the designer</title>
	<link>http://www.barenakedapp.com/the-team/how-we-picked-the-designer</link>
	<description>A behind-the-scenes look at selling dropsend.com</description>
	<pubDate>Mon, 13 Oct 2008 07:56:11 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.2</generator>

	<item>
		<title>by: David Stone</title>
		<link>http://www.barenakedapp.com/the-team/how-we-picked-the-designer#comment-1253</link>
		<pubDate>Tue, 25 Jul 2006 11:35:04 +0000</pubDate>
		<guid>http://www.barenakedapp.com/the-team/how-we-picked-the-designer#comment-1253</guid>
					<description>Hi Avi,

I personally believe that XHTML/CSS is a job better suited to a developer, while there are many designers who can code XHTML/CSS I believe that coders do the code better.

I'm doing both the frontend and backend code for Amigo - Ryan and myself decided at the time that it would be easier not to get another person involved.

However, I think we both agree now that there should have been a seperate developer for frontend and backend code. Not from a quality, but from a time &amp;#38; workload perspective.

Hope that helps.</description>
		<content:encoded><![CDATA[<p>Hi Avi,</p>
<p>I personally believe that XHTML/CSS is a job better suited to a developer, while there are many designers who can code XHTML/CSS I believe that coders do the code better.</p>
<p>I&#8217;m doing both the frontend and backend code for Amigo - Ryan and myself decided at the time that it would be easier not to get another person involved.</p>
<p>However, I think we both agree now that there should have been a seperate developer for frontend and backend code. Not from a quality, but from a time &amp; workload perspective.</p>
<p>Hope that helps.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: avi</title>
		<link>http://www.barenakedapp.com/the-team/how-we-picked-the-designer#comment-1238</link>
		<pubDate>Mon, 24 Jul 2006 17:55:38 +0000</pubDate>
		<guid>http://www.barenakedapp.com/the-team/how-we-picked-the-designer#comment-1238</guid>
					<description>Forgive me in case this was already covered, who is the CSS/XHTML ninja?  Is it your developer or a third person?  Im not looking for a name as much as clarification as to your process.  Also, why did you seperate the functions?  Should designers design and CSS/XHTML experts code in your opinion? (have you noticed better quality is achieved this way?)

Thank you for putting this site up, i cannot tell you how helpful it is.  

Avi</description>
		<content:encoded><![CDATA[<p>Forgive me in case this was already covered, who is the CSS/XHTML ninja?  Is it your developer or a third person?  Im not looking for a name as much as clarification as to your process.  Also, why did you seperate the functions?  Should designers design and CSS/XHTML experts code in your opinion? (have you noticed better quality is achieved this way?)</p>
<p>Thank you for putting this site up, i cannot tell you how helpful it is.  </p>
<p>Avi
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Jeff Levy</title>
		<link>http://www.barenakedapp.com/the-team/how-we-picked-the-designer#comment-446</link>
		<pubDate>Wed, 07 Jun 2006 03:47:08 +0000</pubDate>
		<guid>http://www.barenakedapp.com/the-team/how-we-picked-the-designer#comment-446</guid>
					<description>Just wondering if you could share who the other two designers were that you had considered - or even who was on your shortlist.  I need a good designer.</description>
		<content:encoded><![CDATA[<p>Just wondering if you could share who the other two designers were that you had considered - or even who was on your shortlist.  I need a good designer.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: agenturblog.de &#187; Schulterblick: Ein neues Projekt entsteht</title>
		<link>http://www.barenakedapp.com/the-team/how-we-picked-the-designer#comment-177</link>
		<pubDate>Fri, 19 May 2006 10:17:21 +0000</pubDate>
		<guid>http://www.barenakedapp.com/the-team/how-we-picked-the-designer#comment-177</guid>
					<description>[...] Besonders interessant sind in dieser Dokumentation nicht nur die beschriebenen Prozesse und Budgets, sondern auch die konkreten Fakten der einzelnen Baustellen. So erf&amp;#228;hrt man, dass der f&amp;#252;r das Design beauftragte Jason Santa Maria f&amp;#252;r ein Projekt dieser Gr&amp;#246;&amp;#223;enordnung (ca. 3 Wochen) rund $8.000 berechnet. Fairer Preis. Die einzelnen Schritte der Designfindung sind &amp;#252;ber viele Stationen hier einzusehen. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Besonders interessant sind in dieser Dokumentation nicht nur die beschriebenen Prozesse und Budgets, sondern auch die konkreten Fakten der einzelnen Baustellen. So erf&#228;hrt man, dass der f&#252;r das Design beauftragte Jason Santa Maria f&#252;r ein Projekt dieser Gr&#246;&#223;enordnung (ca. 3 Wochen) rund $8.000 berechnet. Fairer Preis. Die einzelnen Schritte der Designfindung sind &#252;ber viele Stationen hier einzusehen. [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: himbeerBlog &#187; Blog Archive &#187; keine geheimniskrämerei / getting real</title>
		<link>http://www.barenakedapp.com/the-team/how-we-picked-the-designer#comment-67</link>
		<pubDate>Thu, 11 May 2006 14:11:18 +0000</pubDate>
		<guid>http://www.barenakedapp.com/the-team/how-we-picked-the-designer#comment-67</guid>
					<description>[...] Besonders interessant sind in dieser Dokumentation nicht nur die beschriebenen Prozesse und Budgets, sondern auch die konkreten Fakten der einzelnen Baustellen. So erfährt man, dass der für das Design beauftragte Jason Santa Maria für ein Projekt dieser Größenordnung (ca. 3 Wochen) rund $8.000 berechnet. Fairer Preis. Die einzelnen Schritte der Designfindung sind über viele Stationen hier einzusehen. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Besonders interessant sind in dieser Dokumentation nicht nur die beschriebenen Prozesse und Budgets, sondern auch die konkreten Fakten der einzelnen Baustellen. So erfährt man, dass der für das Design beauftragte Jason Santa Maria für ein Projekt dieser Größenordnung (ca. 3 Wochen) rund $8.000 berechnet. Fairer Preis. Die einzelnen Schritte der Designfindung sind über viele Stationen hier einzusehen. [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Matt Carey</title>
		<link>http://www.barenakedapp.com/the-team/how-we-picked-the-designer#comment-48</link>
		<pubDate>Wed, 10 May 2006 21:22:04 +0000</pubDate>
		<guid>http://www.barenakedapp.com/the-team/how-we-picked-the-designer#comment-48</guid>
					<description>No I don't send out one email to potential people, and have not heard of this approach before (though that isn't say it is right or wrong).

The reason I don't is because of what ian mentions above; they will try and be as competitive as possible. 

I want to employ designers/programmers for a fair price who are happy to work with/for me. 

Like you I give them a brief run down of the job and then ask them for a cost estimate. I may say I'm asking other people (more often than not I do say that), and I direct the proposal to them alone. Without the direct competitiveness of feeling &quot;I'm up against xxx, and I really want this job I'll under charge to get it&quot;, they give me a fair cost. 

I have found through experience that people working for what they see as a fair price perform better.

On the other side of the fence, I've been asked to quote for potential work many many times and I've never had a request which showed the other names involved. In some instances I have found out afterwards, but in others I have no idea until I see the finished project. 

I feel happier that way -- pitching takes up a lot of time, and involves a lot of stress and worry, I just don't think it needs to be complicated by being overly competitive.

No personal reflection on what you have done, as it has worked (well) for you and I cannot wait to see the finished app.</description>
		<content:encoded><![CDATA[<p>No I don&#8217;t send out one email to potential people, and have not heard of this approach before (though that isn&#8217;t say it is right or wrong).</p>
<p>The reason I don&#8217;t is because of what ian mentions above; they will try and be as competitive as possible. </p>
<p>I want to employ designers/programmers for a fair price who are happy to work with/for me. </p>
<p>Like you I give them a brief run down of the job and then ask them for a cost estimate. I may say I&#8217;m asking other people (more often than not I do say that), and I direct the proposal to them alone. Without the direct competitiveness of feeling &#8220;I&#8217;m up against xxx, and I really want this job I&#8217;ll under charge to get it&#8221;, they give me a fair cost. </p>
<p>I have found through experience that people working for what they see as a fair price perform better.</p>
<p>On the other side of the fence, I&#8217;ve been asked to quote for potential work many many times and I&#8217;ve never had a request which showed the other names involved. In some instances I have found out afterwards, but in others I have no idea until I see the finished project. </p>
<p>I feel happier that way &#8212; pitching takes up a lot of time, and involves a lot of stress and worry, I just don&#8217;t think it needs to be complicated by being overly competitive.</p>
<p>No personal reflection on what you have done, as it has worked (well) for you and I cannot wait to see the finished app.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: ian</title>
		<link>http://www.barenakedapp.com/the-team/how-we-picked-the-designer#comment-41</link>
		<pubDate>Wed, 10 May 2006 15:53:44 +0000</pubDate>
		<guid>http://www.barenakedapp.com/the-team/how-we-picked-the-designer#comment-41</guid>
					<description>I think it's a great idea to include others in the email. Each of the designers know who they are &quot;up against&quot;, and will try to be as competitive as possible.</description>
		<content:encoded><![CDATA[<p>I think it&#8217;s a great idea to include others in the email. Each of the designers know who they are &#8220;up against&#8221;, and will try to be as competitive as possible.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Gillian Carson</title>
		<link>http://www.barenakedapp.com/the-team/how-we-picked-the-designer#comment-39</link>
		<pubDate>Wed, 10 May 2006 15:03:24 +0000</pubDate>
		<guid>http://www.barenakedapp.com/the-team/how-we-picked-the-designer#comment-39</guid>
					<description>Hi Matt, You mean you don't normally send out one e-mail to all your potential designers on one go?

Can I ask why you don't approve?</description>
		<content:encoded><![CDATA[<p>Hi Matt, You mean you don&#8217;t normally send out one e-mail to all your potential designers on one go?</p>
<p>Can I ask why you don&#8217;t approve?
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Matt Carey</title>
		<link>http://www.barenakedapp.com/the-team/how-we-picked-the-designer#comment-35</link>
		<pubDate>Wed, 10 May 2006 12:24:12 +0000</pubDate>
		<guid>http://www.barenakedapp.com/the-team/how-we-picked-the-designer#comment-35</guid>
					<description>I'm very surprised that you included all three names in one letter to the potential people. Not something I've seen before, or approve of much!</description>
		<content:encoded><![CDATA[<p>I&#8217;m very surprised that you included all three names in one letter to the potential people. Not something I&#8217;ve seen before, or approve of much!
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
