<?xml version="1.0" encoding="utf-8"?><!-- generator="wordpress/1.5.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: On Portfolios</title>
	<link>http://www.joelschou.com/journal/writings/2005/04/on-portfolios</link>
	<description>smarter blogging, finer art, both ears</description>
	<pubDate>Fri, 21 Nov 2008 11:06:56 +0000</pubDate>
	<generator>http://wordpress.org/?v=1.5.2</generator>

	<item>
 		<title>Comment on On Portfolios by: John Pennypacker</title>
		<link>http://www.joelschou.com/journal/writings/2005/04/on-portfolios#comment-41</link>
		<pubDate>Tue, 26 Apr 2005 12:59:29 +0000</pubDate>
		<guid>http://www.joelschou.com/journal/writings/2005/04/on-portfolios#comment-41</guid>
					<description>Quality before quantity.  I think there's a call for a minimum number of pieces though, but you've got it.  I also see that topten is at the bottom of the list, and looks to me like foreshadowing.  </description>
		<content:encoded><![CDATA[	<p>Quality before quantity.  I think there&#8217;s a call for a minimum number of pieces though, but you&#8217;ve got it.  I also see that topten is at the bottom of the list, and looks to me like foreshadowing.  </p>
]]></content:encoded>
				</item>
	<item>
 		<title>Comment on On Portfolios by: joel</title>
		<link>http://www.joelschou.com/journal/writings/2005/04/on-portfolios#comment-36</link>
		<pubDate>Tue, 26 Apr 2005 00:54:02 +0000</pubDate>
		<guid>http://www.joelschou.com/journal/writings/2005/04/on-portfolios#comment-36</guid>
					<description>Whoa, cool. I just pinged myself :) Now, I have to figure out how to make the pingback excerpt not contain all that crap from the #head DIV.</description>
		<content:encoded><![CDATA[	<p>Whoa, cool. I just pinged myself <img src='http://www.joelschou.com/wp/wp-images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  Now, I have to figure out how to make the pingback excerpt not contain all that crap from the #head DIV.</p>
]]></content:encoded>
				</item>
	<item>
 		<title>Comment on On Portfolios by: joelschou.com v3.0  &#8250; journal  &#8250; Revisionist&#8217;s History</title>
		<link>http://www.joelschou.com/journal/writings/2005/04/on-portfolios#comment-35</link>
		<pubDate>Tue, 26 Apr 2005 00:49:20 +0000</pubDate>
		<guid>http://www.joelschou.com/journal/writings/2005/04/on-portfolios#comment-35</guid>
					<description>[...] apri 			tate 			 			small text 			large text 		  	  	  	 	 		journal 	 	  	 	 		 		&amp;#171; On Portfolios &amp;#8226; 		 	 		 			Revisionist&amp;#8217;s History 			Posted on 25th Ap [...]</description>
		<content:encoded><![CDATA[	<p>[&#8230;] apri          tate                        small text          large text                              journal                                 &laquo; On Portfolios &#8226;                               Revisionist&#8217;s History             Posted on 25th Ap [&#8230;]</p>
]]></content:encoded>
				</item>
	<item>
 		<title>Comment on On Portfolios by: joel</title>
		<link>http://www.joelschou.com/journal/writings/2005/04/on-portfolios#comment-34</link>
		<pubDate>Mon, 25 Apr 2005 16:44:42 +0000</pubDate>
		<guid>http://www.joelschou.com/journal/writings/2005/04/on-portfolios#comment-34</guid>
					<description>Have you ever written something late at night that seems to make perfect sense, but upon rereading in the morning it comes across as a bit jumbled and confused? Me either ;)

For the most part, I'm still happy with my choice and the train of thought behind it. Unfortunately, I failed to elaborate enough on one of my points. There are times, I feel, when the person putting together a portfolio needs to show pieces that may not be his or her favorite. There are two reasons. First, a design may be technically solid and very successful, but the designer might hate it. Secondly, (and I did touch on this) a project might represent an important milestone or demonstrate a grasp of a new technology.

See, frankly, I'm not happy with the TopTenQuestions design (it's ?şbercheesy in places, especially the text treatment), but the functionality of that site is what is keeping it in my portfolio (for now). I'm afraid that how it stands right now, it might have an adverse effect on my &quot;qualitative reputation&quot; (now &lt;em&gt;that&lt;/em&gt; was a gag-inducer of a phrase). Once I get the supporting information written, it'll work a lot better, though.

Speaking of hurting my &quot;qualitative reputation,&quot; that green theme is severely lacking in several areas. I'd better get to work on that CSS tonight. I'll also look into the Submit Comment button. You said you can't click it on the blue/black theme? That's odd.</description>
		<content:encoded><![CDATA[	<p>Have you ever written something late at night that seems to make perfect sense, but upon rereading in the morning it comes across as a bit jumbled and confused? Me either <img src='http://www.joelschou.com/wp/wp-images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
	<p>For the most part, I&#8217;m still happy with my choice and the train of thought behind it. Unfortunately, I failed to elaborate enough on one of my points. There are times, I feel, when the person putting together a portfolio needs to show pieces that may not be his or her favorite. There are two reasons. First, a design may be technically solid and very successful, but the designer might hate it. Secondly, (and I did touch on this) a project might represent an important milestone or demonstrate a grasp of a new technology.</p>
	<p>See, frankly, I&#8217;m not happy with the TopTenQuestions design (it&#8217;s ?şbercheesy in places, especially the text treatment), but the functionality of that site is what is keeping it in my portfolio (for now). I&#8217;m afraid that how it stands right now, it might have an adverse effect on my &#8220;qualitative reputation&#8221; (now <em>that</em> was a gag-inducer of a phrase). Once I get the supporting information written, it&#8217;ll work a lot better, though.</p>
	<p>Speaking of hurting my &#8220;qualitative reputation,&#8221; that green theme is severely lacking in several areas. I&#8217;d better get to work on that CSS tonight. I&#8217;ll also look into the Submit Comment button. You said you can&#8217;t click it on the blue/black theme? That&#8217;s odd.</p>
]]></content:encoded>
				</item>
	<item>
 		<title>Comment on On Portfolios by: Shawn</title>
		<link>http://www.joelschou.com/journal/writings/2005/04/on-portfolios#comment-33</link>
		<pubDate>Mon, 25 Apr 2005 13:50:16 +0000</pubDate>
		<guid>http://www.joelschou.com/journal/writings/2005/04/on-portfolios#comment-33</guid>
					<description>Good choice. I personally think that an employer would rather see a stunning few peices than a larger portfolio that has, for lack of a better word, &quot;downers&quot; in it. 
They'd rather see small experiece with potential than a lot of experience with stagnant design.
Now, don't take that the wrong way, I'm not calling your designs stagnant or downers, but just to say that you were right in your decision. 
At least, I think you are.

BTW - I'm in the green theme right now but could not hit the 'submit comment' button in the other theme while using WinFF.</description>
		<content:encoded><![CDATA[	<p>Good choice. I personally think that an employer would rather see a stunning few peices than a larger portfolio that has, for lack of a better word, &#8220;downers&#8221; in it.<br />
They&#8217;d rather see small experiece with potential than a lot of experience with stagnant design.<br />
Now, don&#8217;t take that the wrong way, I&#8217;m not calling your designs stagnant or downers, but just to say that you were right in your decision.<br />
At least, I think you are.</p>
	<p>BTW - I&#8217;m in the green theme right now but could not hit the &#8217;submit comment&#8217; button in the other theme while using WinFF.</p>
]]></content:encoded>
				</item>
</channel>
</rss>
