<?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: Crazy for Queues: A Simple Hack for Complicated Schedules</title>
	<atom:link href="http://www.hackcollege.com/2008/02/29/crazy-for-queues-a-simple-hack-for-complicated-schedules/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.hackcollege.com/2008/02/29/crazy-for-queues-a-simple-hack-for-complicated-schedules/</link>
	<description>HackCollege - Lifehacking for college students</description>
	<pubDate>Sun, 12 Oct 2008 16:47:24 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Chris Osborne</title>
		<link>http://www.hackcollege.com/2008/02/29/crazy-for-queues-a-simple-hack-for-complicated-schedules/#comment-57459</link>
		<dc:creator>Chris Osborne</dc:creator>
		<pubDate>Sun, 09 Mar 2008 02:50:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.hackcollege.com/2008/02/29/crazy-for-queues-a-simple-hack-for-complicated-schedules/#comment-57459</guid>
		<description>I can see the logic behind it, but I don't think it's something that I would be able to utilize.  Still though, something I would pass along.

I have one question though.  Let's say that you don't do what's on top and the work becomes overdue.  Would you still finish that task before anything else or would you move it down the list so that something else doesn't also become overdue?</description>
		<content:encoded><![CDATA[<p>I can see the logic behind it, but I don&#8217;t think it&#8217;s something that I would be able to utilize.  Still though, something I would pass along.</p>
<p>I have one question though.  Let&#8217;s say that you don&#8217;t do what&#8217;s on top and the work becomes overdue.  Would you still finish that task before anything else or would you move it down the list so that something else doesn&#8217;t also become overdue?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: HackCollege Podcast Episode 18: Miami &#124; HackCollege</title>
		<link>http://www.hackcollege.com/2008/02/29/crazy-for-queues-a-simple-hack-for-complicated-schedules/#comment-53175</link>
		<dc:creator>HackCollege Podcast Episode 18: Miami &#124; HackCollege</dc:creator>
		<pubDate>Mon, 03 Mar 2008 23:15:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.hackcollege.com/2008/02/29/crazy-for-queues-a-simple-hack-for-complicated-schedules/#comment-53175</guid>
		<description>[...] Guest Posts [...]</description>
		<content:encoded><![CDATA[<p>[...] Guest Posts [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cal</title>
		<link>http://www.hackcollege.com/2008/02/29/crazy-for-queues-a-simple-hack-for-complicated-schedules/#comment-52956</link>
		<dc:creator>Cal</dc:creator>
		<pubDate>Mon, 03 Mar 2008 18:16:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.hackcollege.com/2008/02/29/crazy-for-queues-a-simple-hack-for-complicated-schedules/#comment-52956</guid>
		<description>@Valery:

You're right on!  A project queue is not a full list of all the next actions. It's an *ordered* list of the next major project chunks you need to get done. You don't choose which of these to do next -- you complete them in the order presented. 

Most of the tasks on your plate are still captured and dealt with in the standard next actions list style.</description>
		<content:encoded><![CDATA[<p>@Valery:</p>
<p>You&#8217;re right on!  A project queue is not a full list of all the next actions. It&#8217;s an *ordered* list of the next major project chunks you need to get done. You don&#8217;t choose which of these to do next &#8212; you complete them in the order presented. </p>
<p>Most of the tasks on your plate are still captured and dealt with in the standard next actions list style.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hir</title>
		<link>http://www.hackcollege.com/2008/02/29/crazy-for-queues-a-simple-hack-for-complicated-schedules/#comment-52608</link>
		<dc:creator>hir</dc:creator>
		<pubDate>Mon, 03 Mar 2008 07:54:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.hackcollege.com/2008/02/29/crazy-for-queues-a-simple-hack-for-complicated-schedules/#comment-52608</guid>
		<description>TYPO:at a lost to
at a loss to</description>
		<content:encoded><![CDATA[<p>TYPO:at a lost to<br />
at a loss to</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Valery</title>
		<link>http://www.hackcollege.com/2008/02/29/crazy-for-queues-a-simple-hack-for-complicated-schedules/#comment-52586</link>
		<dc:creator>Valery</dc:creator>
		<pubDate>Mon, 03 Mar 2008 06:55:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.hackcollege.com/2008/02/29/crazy-for-queues-a-simple-hack-for-complicated-schedules/#comment-52586</guid>
		<description>@Jessica - My two cents on the difference is this: A "projects" list and a "next-action" list have the ability to track of the same items as the queue, however, on a day-to-day basis, you still have to make the decision on where to focus your energy. I know if the next action for a specific project is something I perceive as distateful, then I will put it off until they become an emergency and instead do the next actions that are more interesting to me.

By forming your next-actions for each project into the proposed project queue, you keep yourself from having to make the day-to-day decisions about what to do next (because you just start on the next task for project 1, then go on to next task for project 2, and keep adding the new next tasks to the bottom of the queue) and it keeps you from neglecting projects until they become an emergency. 

That's how I see it, but I'd love to hear someone else's thoughts.</description>
		<content:encoded><![CDATA[<p>@Jessica - My two cents on the difference is this: A &#8220;projects&#8221; list and a &#8220;next-action&#8221; list have the ability to track of the same items as the queue, however, on a day-to-day basis, you still have to make the decision on where to focus your energy. I know if the next action for a specific project is something I perceive as distateful, then I will put it off until they become an emergency and instead do the next actions that are more interesting to me.</p>
<p>By forming your next-actions for each project into the proposed project queue, you keep yourself from having to make the day-to-day decisions about what to do next (because you just start on the next task for project 1, then go on to next task for project 2, and keep adding the new next tasks to the bottom of the queue) and it keeps you from neglecting projects until they become an emergency. </p>
<p>That&#8217;s how I see it, but I&#8217;d love to hear someone else&#8217;s thoughts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jessica</title>
		<link>http://www.hackcollege.com/2008/02/29/crazy-for-queues-a-simple-hack-for-complicated-schedules/#comment-51682</link>
		<dc:creator>Jessica</dc:creator>
		<pubDate>Sun, 02 Mar 2008 01:41:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.hackcollege.com/2008/02/29/crazy-for-queues-a-simple-hack-for-complicated-schedules/#comment-51682</guid>
		<description>I'm still not sure how this is different from a "Projects" list and a "Next Actions" list.</description>
		<content:encoded><![CDATA[<p>I&#8217;m still not sure how this is different from a &#8220;Projects&#8221; list and a &#8220;Next Actions&#8221; list.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cal</title>
		<link>http://www.hackcollege.com/2008/02/29/crazy-for-queues-a-simple-hack-for-complicated-schedules/#comment-51477</link>
		<dc:creator>Cal</dc:creator>
		<pubDate>Sat, 01 Mar 2008 18:57:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.hackcollege.com/2008/02/29/crazy-for-queues-a-simple-hack-for-complicated-schedules/#comment-51477</guid>
		<description>Here's a snapshot of the first few entries on my writer's queue:

------------------------------------------
[ ] blog theme overhaul
------------------------------------------
[ ] finish interviews; submit draft of Flak article
[ ] McSweeney's submission
[ ] next round of interviews for TSC project
...</description>
		<content:encoded><![CDATA[<p>Here&#8217;s a snapshot of the first few entries on my writer&#8217;s queue:</p>
<p>&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;<br />
[ ] blog theme overhaul<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;<br />
[ ] finish interviews; submit draft of Flak article<br />
[ ] McSweeney&#8217;s submission<br />
[ ] next round of interviews for TSC project<br />
&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daryl Tay</title>
		<link>http://www.hackcollege.com/2008/02/29/crazy-for-queues-a-simple-hack-for-complicated-schedules/#comment-51453</link>
		<dc:creator>Daryl Tay</dc:creator>
		<pubDate>Sat, 01 Mar 2008 17:43:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.hackcollege.com/2008/02/29/crazy-for-queues-a-simple-hack-for-complicated-schedules/#comment-51453</guid>
		<description>I was thinking the same thing, we could do with a visual aid!</description>
		<content:encoded><![CDATA[<p>I was thinking the same thing, we could do with a visual aid!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Madeline</title>
		<link>http://www.hackcollege.com/2008/02/29/crazy-for-queues-a-simple-hack-for-complicated-schedules/#comment-51389</link>
		<dc:creator>Madeline</dc:creator>
		<pubDate>Sat, 01 Mar 2008 15:27:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.hackcollege.com/2008/02/29/crazy-for-queues-a-simple-hack-for-complicated-schedules/#comment-51389</guid>
		<description>I like the idea, but I'm having a hard time visualizing what a project queue looks like. Could you upload a sample queue or a screenshot?</description>
		<content:encoded><![CDATA[<p>I like the idea, but I&#8217;m having a hard time visualizing what a project queue looks like. Could you upload a sample queue or a screenshot?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Study Hacks &#187; Blog Archive &#187; Guest Post: Implement a Mechanism-Based Lifestyle</title>
		<link>http://www.hackcollege.com/2008/02/29/crazy-for-queues-a-simple-hack-for-complicated-schedules/#comment-50683</link>
		<dc:creator>Study Hacks &#187; Blog Archive &#187; Guest Post: Implement a Mechanism-Based Lifestyle</dc:creator>
		<pubDate>Fri, 29 Feb 2008 14:19:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.hackcollege.com/2008/02/29/crazy-for-queues-a-simple-hack-for-complicated-schedules/#comment-50683</guid>
		<description>[...] written by our good (and much cooler) friends over at Hack College. If you&#8217;re so inclined, check out the article I wrote for them: how I use &#8220;project queues&#8221; to stay focused. I think we can all agree: Nothing says [...]</description>
		<content:encoded><![CDATA[<p>[...] written by our good (and much cooler) friends over at Hack College. If you&#8217;re so inclined, check out the article I wrote for them: how I use &#8220;project queues&#8221; to stay focused. I think we can all agree: Nothing says [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
