<story><title>Code Fearlessly</title><url>http://cam.ly/blog/2010/12/code-fearlessly/</url></story><parent_chain></parent_chain><comment><author>moron4hire</author><text>Absolutely. Your code is a delusion. You think it does one thing. It does another. Do not care about what the code actually is. Care about what it does. If the code does not meet your needs, then the code is dead (long live the code). Delete it without fear.&lt;p&gt;It&apos;s one thing that drives me nuts about working on teams: coming in to a version-controlled section of code that has had bug fix work done on it with large sections of old code commented out. &quot;This didn&apos;t work, so here is the new stuff.&quot; So why keep the old stuff? &quot;Well, I was worried I&apos;d forget XYZ&quot;. Then address it when you find it. Throw away that old code.&lt;p&gt;I would even go so far as to say that out-of-version-controlled code should be discarded with great haste. If you can&apos;t rewrite the code from scratch, then you don&apos;t understand it. Code lies, cheats, and steals. How do I know it&apos;s the code that is at fault? Because it&apos;s not the person, and people have needs, and those needs still need to be filled, regardless of whether or not the code does what it says it does.</text></comment>
<story><title>Code Fearlessly</title><url>http://cam.ly/blog/2010/12/code-fearlessly/</url></story><parent_chain></parent_chain><comment><author>Aaronontheweb</author><text>I struggle with perfectionism, which is a major productivity killer for developers and a death knell for startups.&lt;p&gt;I&apos;ve adopted a specific mindset in order to push my perfectionistic tendencies aside - I call it &quot;ship shit&quot; - which means the focus is on shipping something out the door even if it is complete and utter shit; ship it with the understanding that you can make it better later.</text></comment>