
<?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: Writing Software To Show My Mom</title>
	<atom:link href="http://mentalpandiculation.com/2010/03/writing-software-to-show-my-mom/feed/" rel="self" type="application/rss+xml" />
	<link>http://mentalpandiculation.com/2010/03/writing-software-to-show-my-mom/</link>
	<description>One Man's Attempt To Find Elegant Code Through Big Words</description>
	<lastBuildDate>Tue, 28 Jun 2011 01:37:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Latish Sehgal</title>
		<link>http://mentalpandiculation.com/2010/03/writing-software-to-show-my-mom/comment-page-1/#comment-142</link>
		<dc:creator>Latish Sehgal</dc:creator>
		<pubDate>Thu, 01 Apr 2010 15:28:21 +0000</pubDate>
		<guid isPermaLink="false">http://mentalpandiculation.com/?p=256#comment-142</guid>
		<description>This sounds familiar :). I think most programmers are distracted by shiny new things easily. And isn&#039;t that the way it should be? I mean I would be wary of working with a programmer who is not excited by new and better framerorks, platforms... 
I think one of the problems (bigger than feedback IMO) we face in personal projects is that there are no deadlines. In our corporate jobs, the deadline to deliver the software is always yesterday, and forces us to concentrate and deliver. Your timeline for a year might be too relaxed. Can&#039;t you practise the Agile/Iterative methodologies that you do at work in your personal projects and ship something in 2 months? This way, if you are still motivated after that, you keep on working on it. If you find something better to do, you take a break and move on to a new one, and reevaluate/revisit this in the future. This might also be the right time to get some feedback. 
As Derek Sivers has pointed out, execution is of utmost importance (http://sivers.org/multiply).</description>
		<content:encoded><![CDATA[<p>This sounds familiar <img src='http://mentalpandiculation.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> . I think most programmers are distracted by shiny new things easily. And isn&#8217;t that the way it should be? I mean I would be wary of working with a programmer who is not excited by new and better framerorks, platforms&#8230;<br />
I think one of the problems (bigger than feedback IMO) we face in personal projects is that there are no deadlines. In our corporate jobs, the deadline to deliver the software is always yesterday, and forces us to concentrate and deliver. Your timeline for a year might be too relaxed. Can&#8217;t you practise the Agile/Iterative methodologies that you do at work in your personal projects and ship something in 2 months? This way, if you are still motivated after that, you keep on working on it. If you find something better to do, you take a break and move on to a new one, and reevaluate/revisit this in the future. This might also be the right time to get some feedback.<br />
As Derek Sivers has pointed out, execution is of utmost importance (<a href="http://sivers.org/multiply" rel="nofollow">http://sivers.org/multiply</a>).</p>
]]></content:encoded>
	</item>
</channel>
</rss>

