<?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: What I Miss About Being Paid Salary</title>
	<atom:link href="http://jessewarden.com/2006/04/what-i-miss-about-being-paid-salary.html/feed" rel="self" type="application/rss+xml" />
	<link>http://jessewarden.com/2006/04/what-i-miss-about-being-paid-salary.html</link>
	<description>A blog on software development, technology, games &#038; movies.</description>
	<pubDate>Thu, 20 Nov 2008 12:59:04 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: TheElder</title>
		<link>http://jessewarden.com/2006/04/what-i-miss-about-being-paid-salary.html#comment-3435</link>
		<dc:creator>TheElder</dc:creator>
		<pubDate>Thu, 13 Apr 2006 21:08:37 +0000</pubDate>
		<guid isPermaLink="false">http://jessewarden.com/?p=996#comment-3435</guid>
		<description>I'd agree on using fix pricing.  That is what I do, hence the previous post. I anticipate bugs in my quote and they pay according to the agreement, not sticking to our agreement, or if they want to add to the project. 

You may try the fix pricing with certain conditions. That may take some time stress off. 

You are still going to have to get project done on time and be honest if you are going to miss the deadline. However, there is something about already having a set price that keeps them from being less forgiving about missing the deadline ( just a bit) :).

Good point Mr. Lee and Mr. Kerman.


</description>
		<content:encoded><![CDATA[<p>I&#8217;d agree on using fix pricing.  That is what I do, hence the previous post. I anticipate bugs in my quote and they pay according to the agreement, not sticking to our agreement, or if they want to add to the project. </p>
<p>You may try the fix pricing with certain conditions. That may take some time stress off. </p>
<p>You are still going to have to get project done on time and be honest if you are going to miss the deadline. However, there is something about already having a set price that keeps them from being less forgiving about missing the deadline ( just a bit) :).</p>
<p>Good point Mr. Lee and Mr. Kerman.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phillip Kerman</title>
		<link>http://jessewarden.com/2006/04/what-i-miss-about-being-paid-salary.html#comment-3434</link>
		<dc:creator>Phillip Kerman</dc:creator>
		<pubDate>Thu, 13 Apr 2006 20:14:40 +0000</pubDate>
		<guid isPermaLink="false">http://jessewarden.com/?p=996#comment-3434</guid>
		<description>Regarding whether to charge for bug fixing... provided that the client really does want the bug fixed, I totally  charge for that time.  I figure if I had programmed it in the first place without any bugs it would have taken longer.  So, if it has bugs it's because they saved money in the other part.  

I also agree that fixed price projects solves much of this.</description>
		<content:encoded><![CDATA[<p>Regarding whether to charge for bug fixing&#8230; provided that the client really does want the bug fixed, I totally  charge for that time.  I figure if I had programmed it in the first place without any bugs it would have taken longer.  So, if it has bugs it&#8217;s because they saved money in the other part.  </p>
<p>I also agree that fixed price projects solves much of this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom Lee</title>
		<link>http://jessewarden.com/2006/04/what-i-miss-about-being-paid-salary.html#comment-3433</link>
		<dc:creator>Tom Lee</dc:creator>
		<pubDate>Thu, 13 Apr 2006 19:39:17 +0000</pubDate>
		<guid isPermaLink="false">http://jessewarden.com/?p=996#comment-3433</guid>
		<description>That's one reason I went to lump-sum contracts.  My promise is 'the project is done when you're happy with it' and I get to take whatever time I need to do it.  My clients are happy because they know they'll be satisfied in the end, and I'm happy because I'm not on the clock.</description>
		<content:encoded><![CDATA[<p>That&#8217;s one reason I went to lump-sum contracts.  My promise is &#8216;the project is done when you&#8217;re happy with it&#8217; and I get to take whatever time I need to do it.  My clients are happy because they know they&#8217;ll be satisfied in the end, and I&#8217;m happy because I&#8217;m not on the clock.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TheElder</title>
		<link>http://jessewarden.com/2006/04/what-i-miss-about-being-paid-salary.html#comment-3432</link>
		<dc:creator>TheElder</dc:creator>
		<pubDate>Thu, 13 Apr 2006 16:15:37 +0000</pubDate>
		<guid isPermaLink="false">http://jessewarden.com/?p=996#comment-3432</guid>
		<description>I haven't had EXTENSIVE experience dealing with BIG problems as you probably have. Most of the time the solutions that I provide are pretty simple.

However, for those times that aren't as easy going where I have ran into problems. I'm usually honest.

&lt;b&gt;Client: &lt;/b&gt;'How long will it take to fix the problem?'
&lt;b&gt;Me: &lt;/b&gt;'Honestly, I do not know. This is a new issue for me, but I'm sure I'll find the problem.'

Now....... depending on the client that may prompt:

&lt;b&gt;'You don't know! You Ripoff CON!' &lt;/b&gt;

However, honesty is my best policy and so far the response has been. 

&lt;b&gt;'Well, I trust you, I know you are going to figure it out. That's why we hired you.' &lt;/b&gt;

That may sound fairy tale like, and maybe I haven't got enough experience to get the response before that. I just try to make sure the client trust me to full extent and to expect problems before we step forward.</description>
		<content:encoded><![CDATA[<p>I haven&#8217;t had EXTENSIVE experience dealing with BIG problems as you probably have. Most of the time the solutions that I provide are pretty simple.</p>
<p>However, for those times that aren&#8217;t as easy going where I have ran into problems. I&#8217;m usually honest.</p>
<p><b>Client: </b>&#8216;How long will it take to fix the problem?&#8217;<br />
<b>Me: </b>&#8216;Honestly, I do not know. This is a new issue for me, but I&#8217;m sure I&#8217;ll find the problem.&#8217;</p>
<p>Now&#8230;&#8230;. depending on the client that may prompt:</p>
<p><b>&#8216;You don&#8217;t know! You Ripoff CON!&#8217; </b></p>
<p>However, honesty is my best policy and so far the response has been. </p>
<p><b>&#8216;Well, I trust you, I know you are going to figure it out. That&#8217;s why we hired you.&#8217; </b></p>
<p>That may sound fairy tale like, and maybe I haven&#8217;t got enough experience to get the response before that. I just try to make sure the client trust me to full extent and to expect problems before we step forward.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sean</title>
		<link>http://jessewarden.com/2006/04/what-i-miss-about-being-paid-salary.html#comment-3431</link>
		<dc:creator>Sean</dc:creator>
		<pubDate>Thu, 13 Apr 2006 15:41:39 +0000</pubDate>
		<guid isPermaLink="false">http://jessewarden.com/?p=996#comment-3431</guid>
		<description>the other part of that 'how long should I spend on this?' that can get sticky is figuring out how much of the debugging time is billable.. trying to be both fair to the client AND yourself, and sometimes having to accept (as Phillip pointed out) that the client really doesn't care that it's not perfect.. and you have to let that bug go out into the wild...</description>
		<content:encoded><![CDATA[<p>the other part of that &#8216;how long should I spend on this?&#8217; that can get sticky is figuring out how much of the debugging time is billable.. trying to be both fair to the client AND yourself, and sometimes having to accept (as Phillip pointed out) that the client really doesn&#8217;t care that it&#8217;s not perfect.. and you have to let that bug go out into the wild&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
