<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
     xmlns:admin="http://webns.net/mvcb/"
     xmlns:content="http://purl.org/rss/1.0/modules/content/"
     xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
	<channel>
	  <title>Ask MetaFilter questions tagged with costbenefit</title>
      <link>http://ask.metafilter.com/tags/costbenefit</link>
      <description>Questions tagged with 'costbenefit' at Ask MetaFilter.</description>
	  <pubDate>Wed, 23 Apr 2008 14:13:55 -0800</pubDate> <lastBuildDate>Wed, 23 Apr 2008 14:13:55 -0800</lastBuildDate>

      <language>en-us</language>
	  <docs>http://blogs.law.harvard.edu/tech/rss</docs>
	  <ttl>60</ttl>	  
	<item>
	<title>GTD Cost vs. Benefit Analysis</title>
	<link>http://ask.metafilter.com/89628/GTD%2DCost%2Dvs%2DBenefit%2DAnalysis</link>	
	<description>GTD Filter: How do I best decide what my next action should be? I.e, how do I map out the Cost vs. Benefit? I always have the choice between different things to do. I could work on my clients project, I could work on my personal project, I could study for school, I could go out and get me some needle and thread, I could call a friend, I could watch the new episode of Lost, I could research and buy some parts for my hobby robot.&lt;br&gt;
&lt;br&gt;
There are always a lot of things to be done, and these things will all have to be done sooner or later. The list also never ends, because there is always something pending for the client, my project is never done, housework is a constant thing, etc.&lt;br&gt;
&lt;br&gt;
I need a way of somehow being able to decide which task should be done right now, and which should be moved forward. What&apos;s the best system to decide this?&lt;br&gt;
&lt;br&gt;
Important is that there is constant rotation - each thing needs some time so it does not fall behind the others. Also, I don&apos;t want to relearn a whole new GTD system, I just want a technical solution for how to keep my next actions rotating, with each project gettings its fair share.</description>
	<guid isPermaLink="false">tag:ask.metafilter.com,2008:site.89628</guid>
	<pubDate>Wed, 23 Apr 2008 14:13:55 -0800</pubDate>
	<category>costbenefit</category>
	<category>gtb</category>
	<dc:creator>markovich</dc:creator>
	</item>
	<item>
	<title>Fix it or junk it?</title>
	<link>http://ask.metafilter.com/36130/Fix%2Dit%2Dor%2Djunk%2Dit</link>	
	<description>At what point is a car not worth repairing? My 10-year-old 130k-mile Saturn is showing its age pretty badly&#8212;leaking oil, disturbing noise coming from the front end, crumbling exhaust system.  I&apos;m having a tough time coming up with a satisfying way to determine if it makes financial sense to pay for the repairs or to just ditch the car and buy a new one (living carless isn&apos;t an option, cool as it would be).&lt;br&gt;
&lt;br&gt;
The Internet tells me the car&apos;s currently worth $700; one common calculation I hear is that if the repairs cost more than $700, they&apos;re not worth making.  But on the other hand, even if the repairs were to cost twice the value of the car, $1400 is a lot less than the expense I&apos;d incur getting a new one.&lt;br&gt;
&lt;br&gt;
So I guess what I&apos;m looking for is advice/perspectives on how these factors play against each other.  Does anyone have any experience bringing an aging car like this back from the brink without essentially taking a large pile of money out into the garage and lighting it on fire?</description>
	<guid isPermaLink="false">tag:ask.metafilter.com,2006:site.36130</guid>
	<pubDate>Tue, 11 Apr 2006 08:59:34 -0800</pubDate>
	<category>carrepair</category>
	<category>carreplacement</category>
	<category>cars</category>
	<category>costbenefit</category>
	<dc:creator>COBRA!</dc:creator>
	</item>
	
	</channel>
</rss>

