<?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: How to take a break when programming</title>
	<atom:link href="http://ryan.kohn.ca/articles/how-to-take-a-break-when-programming/feed/" rel="self" type="application/rss+xml" />
	<link>http://ryan.kohn.ca/articles/how-to-take-a-break-when-programming/</link>
	<description>a passionate Toronto-area software developer.</description>
	<lastBuildDate>Thu, 16 Apr 2009 14:23:27 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Ryan</title>
		<link>http://ryan.kohn.ca/articles/how-to-take-a-break-when-programming/#comment-5</link>
		<dc:creator>Ryan</dc:creator>
		<pubDate>Tue, 31 Mar 2009 16:30:35 +0000</pubDate>
		<guid isPermaLink="false">http://ryan.kohn.ca/articles/?p=27#comment-5</guid>
		<description>Thanks, Ayla!

Handling an unexpected interruption is a bit tricky. You need to be able to estimate how long you&#039;ll be away from your work. I&#039;d say that, in most cases, someone interrupts you to ask a quick question that has a quick answer. So you can go ahead and answer it.

But sometimes you&#039;ll have to deal with a client request, be pulled away for a lengthy meeting, or realize that quick question doesn&#039;t have a quick answer. As soon as you realize you&#039;re going to be away for a while, you need to start preparing.

It&#039;s perfectly okay to tell the person interrupting you that you just need a few minutes to finish things up. Sometimes when I do this, the person continues to stand over me, at which point I politely suggest that I&#039;ll give them a call when I&#039;m ready.

Not only does this allow you to get back into your work quickly, but you&#039;ll also have a clear head to handle the interruption.</description>
		<content:encoded><![CDATA[<p>Thanks, Ayla!</p>
<p>Handling an unexpected interruption is a bit tricky. You need to be able to estimate how long you&#8217;ll be away from your work. I&#8217;d say that, in most cases, someone interrupts you to ask a quick question that has a quick answer. So you can go ahead and answer it.</p>
<p>But sometimes you&#8217;ll have to deal with a client request, be pulled away for a lengthy meeting, or realize that quick question doesn&#8217;t have a quick answer. As soon as you realize you&#8217;re going to be away for a while, you need to start preparing.</p>
<p>It&#8217;s perfectly okay to tell the person interrupting you that you just need a few minutes to finish things up. Sometimes when I do this, the person continues to stand over me, at which point I politely suggest that I&#8217;ll give them a call when I&#8217;m ready.</p>
<p>Not only does this allow you to get back into your work quickly, but you&#8217;ll also have a clear head to handle the interruption.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ayla</title>
		<link>http://ryan.kohn.ca/articles/how-to-take-a-break-when-programming/#comment-4</link>
		<dc:creator>Ayla</dc:creator>
		<pubDate>Tue, 31 Mar 2009 15:59:51 +0000</pubDate>
		<guid isPermaLink="false">http://ryan.kohn.ca/articles/?p=27#comment-4</guid>
		<description>Great Post! 
How do you suggest handling interruptions that force you to take an unexpected break?</description>
		<content:encoded><![CDATA[<p>Great Post!<br />
How do you suggest handling interruptions that force you to take an unexpected break?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

