<?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: On giving up on bad ideas</title>
	<atom:link href="http://777h.org/blog/archives/7/feed" rel="self" type="application/rss+xml" />
	<link>http://777h.org/blog/archives/7</link>
	<description>wastes of money and time</description>
	<lastBuildDate>Sat, 17 Dec 2011 20:14:31 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Ryan</title>
		<link>http://777h.org/blog/archives/7#comment-4</link>
		<dc:creator>Ryan</dc:creator>
		<pubDate>Fri, 23 Mar 2007 22:48:07 +0000</pubDate>
		<guid isPermaLink="false">http://777h.org/blog/archives/7#comment-4</guid>
		<description>I think that it&#039;s time to give up on something when you:
a) Realize that something is crap
b) Have learned &lt;i&gt;why&lt;/i&gt; the thing is crap, so you don&#039;t make the same mistakes.

If you&#039;re only past part a, you need to keep looking at the idea until you understand what&#039;s wrong with it, what makes it bad.  This probably means you keep working on it until you find yourself in a corner unable to improve the idea/script.  Then you&#039;ll be able to do some retrospection and say &quot;Here&#039;s where this went wrong.&quot;

And then the trick is to make sure you don&#039;t make those mistakes again.  It&#039;s a lot harder in a creative process than it is other things, but it&#039;s gotta be doable.

And nothing is more valuable than constructive criticism, even if it can be hard to take (I know I&#039;m horrible with it).  So if there&#039;s a community out there who can review it and give you useful feedback, leverage it.</description>
		<content:encoded><![CDATA[<p>I think that it&#8217;s time to give up on something when you:<br />
a) Realize that something is crap<br />
b) Have learned <i>why</i> the thing is crap, so you don&#8217;t make the same mistakes.</p>
<p>If you&#8217;re only past part a, you need to keep looking at the idea until you understand what&#8217;s wrong with it, what makes it bad.  This probably means you keep working on it until you find yourself in a corner unable to improve the idea/script.  Then you&#8217;ll be able to do some retrospection and say &#8220;Here&#8217;s where this went wrong.&#8221;</p>
<p>And then the trick is to make sure you don&#8217;t make those mistakes again.  It&#8217;s a lot harder in a creative process than it is other things, but it&#8217;s gotta be doable.</p>
<p>And nothing is more valuable than constructive criticism, even if it can be hard to take (I know I&#8217;m horrible with it).  So if there&#8217;s a community out there who can review it and give you useful feedback, leverage it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

