<?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"
	>
<channel>
	<title>Comments on: Dealing With Procrastination</title>
	<atom:link href="http://climbtothestars.org/archives/2007/09/11/dealing-with-procrastination/feed/" rel="self" type="application/rss+xml" />
	<link>http://climbtothestars.org/archives/2007/09/11/dealing-with-procrastination/</link>
	<description>More than just a blog.</description>
	<pubDate>Wed, 09 Jul 2008 05:12:13 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: links for 2007-09-13 &#171; Matthew Henty</title>
		<link>http://climbtothestars.org/archives/2007/09/11/dealing-with-procrastination/#comment-265567</link>
		<dc:creator>links for 2007-09-13 &#171; Matthew Henty</dc:creator>
		<pubDate>Thu, 13 Sep 2007 06:28:18 +0000</pubDate>
		<guid isPermaLink="false">http://climbtothestars.org/archives/2007/09/11/dealing-with-procrastination/#comment-265567</guid>
		<description>&lt;p&gt;[...] Dealing With Procrastination (tags: productivity procrastination) [...]&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>[...] Dealing With Procrastination (tags: productivity procrastination) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hartwig</title>
		<link>http://climbtothestars.org/archives/2007/09/11/dealing-with-procrastination/#comment-264632</link>
		<dc:creator>hartwig</dc:creator>
		<pubDate>Tue, 11 Sep 2007 15:31:07 +0000</pubDate>
		<guid isPermaLink="false">http://climbtothestars.org/archives/2007/09/11/dealing-with-procrastination/#comment-264632</guid>
		<description>&lt;p&gt;I appreciate reading such a thoughtful analysis of this important topic which has so far-reaching consequences for so many people - including me. Obviously one strategy for dealing with procrastination (Does anyone know a nice German translation for that?) does not work for all.&lt;/p&gt;

&lt;p&gt;I personally find it rather impossible to work an "hard" projects - which are often the subject of delayed start - for only 30 minutes. Even the prospect of not having at least three hours for such a start of a new big job stops me from working on it. Once I am involved with a subject I do not find it hard to stick with it for hours on end.&lt;/p&gt;

&lt;p&gt;So here is my strategy:
Split the todo-list into "small and useful" (like: fiddle with website, do bookkeeping, ...) and "large and hairy" (like: write a specification, write a large program, ...). Of course each of these lists also needs to be sorted according to priorities (deadlines etc.)
Now start with the item that you least like and that is most pressing, given the time available for it today. Thus, if you only have 30 minutes left, don't start on any big, hairy item. If you do have ample time, however, start with the one you like least.
When you get tired of it, do a small useful one and return to the current big one. When you have done all the small useful ones, switch back and forth between two big ones. Promise yourself the pleasure of working on a nice big one (develop a new program with new tools) as a reward for having finished the necessary and pressing ones (write the controversial strategy paper for a big project).&lt;/p&gt;

&lt;p&gt;I find that I can get involved even with stupid administrative jobs once I have started them if the reward is available. The only real difficult show-stopper is difficult relationships with people for who you write or develop. I have not really found a solution for that problem. I try to avoid working on such projects for such customers.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>I appreciate reading such a thoughtful analysis of this important topic which has so far-reaching consequences for so many people - including me. Obviously one strategy for dealing with procrastination (Does anyone know a nice German translation for that?) does not work for all.</p>
<p>I personally find it rather impossible to work an &#8220;hard&#8221; projects - which are often the subject of delayed start - for only 30 minutes. Even the prospect of not having at least three hours for such a start of a new big job stops me from working on it. Once I am involved with a subject I do not find it hard to stick with it for hours on end.</p>
<p>So here is my strategy:<br />
Split the todo-list into &#8220;small and useful&#8221; (like: fiddle with website, do bookkeeping, &#8230;) and &#8220;large and hairy&#8221; (like: write a specification, write a large program, &#8230;). Of course each of these lists also needs to be sorted according to priorities (deadlines etc.)<br />
Now start with the item that you least like and that is most pressing, given the time available for it today. Thus, if you only have 30 minutes left, don&#8217;t start on any big, hairy item. If you do have ample time, however, start with the one you like least.<br />
When you get tired of it, do a small useful one and return to the current big one. When you have done all the small useful ones, switch back and forth between two big ones. Promise yourself the pleasure of working on a nice big one (develop a new program with new tools) as a reward for having finished the necessary and pressing ones (write the controversial strategy paper for a big project).</p>
<p>I find that I can get involved even with stupid administrative jobs once I have started them if the reward is available. The only real difficult show-stopper is difficult relationships with people for who you write or develop. I have not really found a solution for that problem. I try to avoid working on such projects for such customers.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
