<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Supple software comments on Multitasking as procrastination</title>
    <link>http://www.supplesoftware.com/</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description>Supple software comments</description>
    <item>
      <title>"Multitasking as procrastination" by petrovg</title>
      <description>&lt;p&gt;The problem with having many tasks on  hand is that you always have something easier to do. So when you hit a bit of a rough patch, you just switch to an easier one. Which is why I&amp;#8217;m now writing this rant instead of organising my summer holiday in Central America.&lt;/p&gt;

&lt;p&gt;Don&amp;#8217;t know if it happens to other people, but it certainly happens to me. And then all the tasks become stuck right at the rough spot, so you have trouble deciding which one of the many stuck ones to target and spend more time switching than actually achieving something. OK that&amp;#8217;s enough, let&amp;#8217;s find something easier to do now&amp;#8230;&amp;#8230;&lt;/p&gt;

&lt;p&gt;PS. Which, I guess, explains why people complain that they spend X hours a day reading/replying to/writing emails. Hm&amp;#8230; this doesn&amp;#8217;t seem to be going anywhere, ooh, look! here comes an email, let&amp;#8217;s follow it up&amp;#8230;..&lt;/p&gt;

&lt;p&gt;PS2. &amp;#8230;and why pair programming is more efficient than solo-programming - you just can&amp;#8217;t switch every time you hit a wall&amp;#8230;.&lt;/p&gt;

</description>
      <pubDate>Thu, 12 Apr 2007 12:08:00 PDT</pubDate>
      <guid>&lt;a href="/articles/2007/04/12/multitasking-as-procrastination"&gt;Multitasking as procrastination&lt;/a&gt;</guid>
      <link>&lt;a href="/articles/2007/04/12/multitasking-as-procrastination"&gt;Multitasking as procrastination&lt;/a&gt;</link>
    </item>
  </channel>
</rss>
