http://blogs.msdn.com/b/steverowe/archive/2007/07/05/yak-shaving.aspx(Last post inspired by Dreaming in code...I think) There is a problem in building software. We don't know how to estimate how long it will take to build something. A 2-week project takes 4. A one month project takes six. Why is that? There are a lot ofen-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.msdn.com/b/steverowe/archive/2007/07/05/yak-shaving.aspx#3802480Tue, 10 Jul 2007 22:42:34 GMT91d46819-8472-40ad-a661-2c78acb4018c:3802480Jon Richards<p>One of my favorite quotes is, &quot;Weeks of coding can save hours of planning.&quot;</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=3802480" width="1" height="1">http://blogs.msdn.com/b/steverowe/archive/2007/07/05/yak-shaving.aspx#3720366Fri, 06 Jul 2007 06:56:10 GMT91d46819-8472-40ad-a661-2c78acb4018c:3720366Andrew<p>And all too often building the tangential tool is more interesting (and often easier) than the problem itself so developers will find all kind of reasons why it is necessary to build a new compiler/test framework/result parser etc. rather than actually doing hard work of creating a shipping product.</p> <p>In my experience, figuring out which of these tools is actually worth the cost of building &amp; maintaining them is a good assignment for the technical lead(s) on a project.</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=3720366" width="1" height="1">