<?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: HOWTO: Manage a contractor</title>
	<atom:link href="http://losingfight.com/blog/2006/12/02/howto-manage-a-contractor/feed/" rel="self" type="application/rss+xml" />
	<link>http://losingfight.com/blog/2006/12/02/howto-manage-a-contractor/</link>
	<description>because i don&#039;t write software for windows</description>
	<lastBuildDate>Tue, 31 Jan 2012 00:17:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: tyler</title>
		<link>http://losingfight.com/blog/2006/12/02/howto-manage-a-contractor/comment-page-1/#comment-347</link>
		<dc:creator>tyler</dc:creator>
		<pubDate>Sat, 20 Oct 2007 03:59:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.losingfight.com/blog/2006/12/02/howto-manage-a-contractor/#comment-347</guid>
		<description>Agreed.  20 +/- years as a contractor and I&#039;ve experienced too many of the things you suggest a client not do.   I&#039;m going to be handing the url to your blog entry to future new clients as a primer... thanks for taking the time to write it out well.

Oh, one proposed edit:  &quot;bug base&quot;  should probably read &quot;bug database&quot;; I knew what you meant, but potential clients might not.

A post on what a specification should be and what it shouldn&#039;t be would be a good follow-up to this post, if you haven&#039;t done it already.

One on what a good bug report contains (and doesn&#039;t contain) is another article that would work well linked off of this post.

peace.</description>
		<content:encoded><![CDATA[<p>Agreed.  20 +/- years as a contractor and I&#8217;ve experienced too many of the things you suggest a client not do.   I&#8217;m going to be handing the url to your blog entry to future new clients as a primer&#8230; thanks for taking the time to write it out well.</p>
<p>Oh, one proposed edit:  &#8220;bug base&#8221;  should probably read &#8220;bug database&#8221;; I knew what you meant, but potential clients might not.</p>
<p>A post on what a specification should be and what it shouldn&#8217;t be would be a good follow-up to this post, if you haven&#8217;t done it already.</p>
<p>One on what a good bug report contains (and doesn&#8217;t contain) is another article that would work well linked off of this post.</p>
<p>peace.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Batton</title>
		<link>http://losingfight.com/blog/2006/12/02/howto-manage-a-contractor/comment-page-1/#comment-346</link>
		<dc:creator>Dave Batton</dc:creator>
		<pubDate>Sun, 03 Dec 2006 21:32:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.losingfight.com/blog/2006/12/02/howto-manage-a-contractor/#comment-346</guid>
		<description>Great post! I&#039;ve been an independent contractor for about 15 years now, and it&#039;s always comforting when I&#039;m reminded that others have similar problems with clients. Thanks!</description>
		<content:encoded><![CDATA[<p>Great post! I&#8217;ve been an independent contractor for about 15 years now, and it&#8217;s always comforting when I&#8217;m reminded that others have similar problems with clients. Thanks!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

