<?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: What all programmers have in common</title>
	<atom:link href="http://coliveira.net/software/what-all-programmers-have-in-common/feed/" rel="self" type="application/rss+xml" />
	<link>http://coliveira.net/software/what-all-programmers-have-in-common/</link>
	<description>Some Ideas by Carlos Oliveira</description>
	<lastBuildDate>Wed, 01 Sep 2010 02:24:06 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Duan Lian</title>
		<link>http://coliveira.net/software/what-all-programmers-have-in-common/comment-page-1/#comment-147</link>
		<dc:creator>Duan Lian</dc:creator>
		<pubDate>Mon, 01 Jun 2009 08:41:09 +0000</pubDate>
		<guid isPermaLink="false">http://coliveira.net/?p=246#comment-147</guid>
		<description>I translated this article into Chinese. The url is http://chemhack.com/cn/2009/06/what-all-programmers-have-in-common/ . The translation is for non-profit purpose. 

If you&#039;re not comfortable with this translation, please let me know.</description>
		<content:encoded><![CDATA[<p>I translated this article into Chinese. The url is <a href="http://chemhack.com/cn/2009/06/what-all-programmers-have-in-common/" rel="nofollow">http://chemhack.com/cn/2009/06/what-all-programmers-have-in-common/</a> . The translation is for non-profit purpose. </p>
<p>If you&#8217;re not comfortable with this translation, please let me know.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ??????? &#187; ChemHack ????</title>
		<link>http://coliveira.net/software/what-all-programmers-have-in-common/comment-page-1/#comment-146</link>
		<dc:creator>??????? &#187; ChemHack ????</dc:creator>
		<pubDate>Mon, 01 Jun 2009 08:39:56 +0000</pubDate>
		<guid isPermaLink="false">http://coliveira.net/?p=246#comment-146</guid>
		<description>[...] Lian???Carlos Oliveira?What all programmers have in common? [...]</description>
		<content:encoded><![CDATA[<p>[...] Lian???Carlos Oliveira?What all programmers have in common? [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ??????? &#187; ChemHack ????</title>
		<link>http://coliveira.net/software/what-all-programmers-have-in-common/comment-page-1/#comment-145</link>
		<dc:creator>??????? &#187; ChemHack ????</dc:creator>
		<pubDate>Mon, 01 Jun 2009 08:36:33 +0000</pubDate>
		<guid isPermaLink="false">http://coliveira.net/?p=246#comment-145</guid>
		<description>[...] Lian???Carlos Oliveira?What all programmers have in common? [...]</description>
		<content:encoded><![CDATA[<p>[...] Lian???Carlos Oliveira?What all programmers have in common? [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Lewis</title>
		<link>http://coliveira.net/software/what-all-programmers-have-in-common/comment-page-1/#comment-90</link>
		<dc:creator>Mike Lewis</dc:creator>
		<pubDate>Wed, 13 May 2009 13:19:52 +0000</pubDate>
		<guid isPermaLink="false">http://coliveira.net/?p=246#comment-90</guid>
		<description>What works for me is to 
(1) estimate the time needed to complete a project if there are no major problems along the way, then double it 
(2) do two versions of the project at the same time.  The first version is what the customer wants.  The second version is a list of all the ideas my programming team comes up with while doing the first version.  Acknowledging their ideas by keeping a list (a) makes them feel more engaged with their work (b) keeps my team thinking about better ways of doing things (c) stops them from implementing their ideas before version 1 is finished (d) gives us a list of improvements for the next version to keep us ahead of the competition.</description>
		<content:encoded><![CDATA[<p>What works for me is to<br />
(1) estimate the time needed to complete a project if there are no major problems along the way, then double it<br />
(2) do two versions of the project at the same time.  The first version is what the customer wants.  The second version is a list of all the ideas my programming team comes up with while doing the first version.  Acknowledging their ideas by keeping a list (a) makes them feel more engaged with their work (b) keeps my team thinking about better ways of doing things (c) stops them from implementing their ideas before version 1 is finished (d) gives us a list of improvements for the next version to keep us ahead of the competition.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sharkey</title>
		<link>http://coliveira.net/software/what-all-programmers-have-in-common/comment-page-1/#comment-89</link>
		<dc:creator>Sharkey</dc:creator>
		<pubDate>Wed, 13 May 2009 00:08:44 +0000</pubDate>
		<guid isPermaLink="false">http://coliveira.net/?p=246#comment-89</guid>
		<description>I don&#039;t think this trait is limited to programmers; it&#039;s a general property of human psychology. 

http://www.overcomingbias.com/2007/09/planning-fallac.html

Personally, I like the following metric (I think I picked it up from Old New Thing): double the number and increase the unit. 3 hours becomes 6 days, 2 weeks is 4 months, etc. It&#039;s been quite accurate so far :)</description>
		<content:encoded><![CDATA[<p>I don&#8217;t think this trait is limited to programmers; it&#8217;s a general property of human psychology. </p>
<p><a href="http://www.overcomingbias.com/2007/09/planning-fallac.html" rel="nofollow">http://www.overcomingbias.com/2007/09/planning-fallac.html</a></p>
<p>Personally, I like the following metric (I think I picked it up from Old New Thing): double the number and increase the unit. 3 hours becomes 6 days, 2 weeks is 4 months, etc. It&#8217;s been quite accurate so far :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: m</title>
		<link>http://coliveira.net/software/what-all-programmers-have-in-common/comment-page-1/#comment-88</link>
		<dc:creator>m</dc:creator>
		<pubDate>Tue, 12 May 2009 23:07:59 +0000</pubDate>
		<guid isPermaLink="false">http://coliveira.net/?p=246#comment-88</guid>
		<description>Most of the experienced programmers I know are actually very pessimistic about how long something will take.

It is the people who do not write software (managers, customers, etc.) who tend to underestimate and insist on unrealistic schedules.

Programming projects are almost always behind schedule because the people who have the final say on schedules are managers who do not understand the process of writing software.</description>
		<content:encoded><![CDATA[<p>Most of the experienced programmers I know are actually very pessimistic about how long something will take.</p>
<p>It is the people who do not write software (managers, customers, etc.) who tend to underestimate and insist on unrealistic schedules.</p>
<p>Programming projects are almost always behind schedule because the people who have the final say on schedules are managers who do not understand the process of writing software.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: coliveira</title>
		<link>http://coliveira.net/software/what-all-programmers-have-in-common/comment-page-1/#comment-87</link>
		<dc:creator>coliveira</dc:creator>
		<pubDate>Tue, 12 May 2009 21:06:00 +0000</pubDate>
		<guid isPermaLink="false">http://coliveira.net/?p=246#comment-87</guid>
		<description>@Alvin,
Thanks for your comment. I agree this is applicable to many knowledge workers. It is just that programmers are very susceptible to this kind of problem.</description>
		<content:encoded><![CDATA[<p>@Alvin,<br />
Thanks for your comment. I agree this is applicable to many knowledge workers. It is just that programmers are very susceptible to this kind of problem.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alvin</title>
		<link>http://coliveira.net/software/what-all-programmers-have-in-common/comment-page-1/#comment-86</link>
		<dc:creator>Alvin</dc:creator>
		<pubDate>Tue, 12 May 2009 20:58:47 +0000</pubDate>
		<guid isPermaLink="false">http://coliveira.net/?p=246#comment-86</guid>
		<description>I would like to thank you for your tip. As a web designer, this might be applicable to me as well.</description>
		<content:encoded><![CDATA[<p>I would like to thank you for your tip. As a web designer, this might be applicable to me as well.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
