<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>thaumaturgy</author><text>No, this is still a payment against technical debt. From the top of Martin Fowler&amp;#x27;s article:&lt;p&gt;&amp;quot;The extra effort that it takes to add new features is the interest paid on the debt.&amp;quot;&lt;p&gt;If adding a new feature starts with, &amp;quot;just throw out all the code and start from scratch&amp;quot;, that&amp;#x27;s a much larger cost over the long term than building code that&amp;#x27;s easier to maintain and refresh.</text><parent_chain><item><author>varjag</author><text>&amp;gt; 1. Most code will be rewritten every 2 to 3 years.&lt;p&gt;a.k.a. defaulting on the technical debt</text></item><item><author>rsweeney21</author><text>I cut my teeth as a developer on the Windows operating system. Because we were a platform, we had learned that when we shipped an API it became more or less permanent. So technical debt was a huge part of our planning and thought process.&lt;p&gt;When I joined Netflix I was assigned to add DASH support to the Silverlight web player. I spent weeks working on the new architecture, refactoring the streaming code, etc. One day my manager stopped by my desk and said that &amp;quot;I needed to wrap it up. It was taking too long.&amp;quot; I was still weeks away from being done. I explained to that I was cleaning up a ton of technical debt and that&amp;#x27;s why it was taking so long.&lt;p&gt;He explained to me that they had different values on his team.&lt;p&gt;1. Most code will be rewritten every 2 to 3 years.
2. For code that doesn&amp;#x27;t get rewritten often, preserving battle tested code trumps paying down technical debt&lt;p&gt;Just remember that technical debt doesn&amp;#x27;t apply to all software.</text></item></parent_chain></comment><story><title>Technical Debt</title><url>https://martinfowler.com/bliki/TechnicalDebt.html</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>ramraj07</author><text>Not necessarily. More like an asset that has finished it&amp;#x27;s designed lifespan and the org has moved to a new asset.</text><parent_chain><item><author>varjag</author><text>&amp;gt; 1. Most code will be rewritten every 2 to 3 years.&lt;p&gt;a.k.a. defaulting on the technical debt</text></item><item><author>rsweeney21</author><text>I cut my teeth as a developer on the Windows operating system. Because we were a platform, we had learned that when we shipped an API it became more or less permanent. So technical debt was a huge part of our planning and thought process.&lt;p&gt;When I joined Netflix I was assigned to add DASH support to the Silverlight web player. I spent weeks working on the new architecture, refactoring the streaming code, etc. One day my manager stopped by my desk and said that &amp;quot;I needed to wrap it up. It was taking too long.&amp;quot; I was still weeks away from being done. I explained to that I was cleaning up a ton of technical debt and that&amp;#x27;s why it was taking so long.&lt;p&gt;He explained to me that they had different values on his team.&lt;p&gt;1. Most code will be rewritten every 2 to 3 years.
2. For code that doesn&amp;#x27;t get rewritten often, preserving battle tested code trumps paying down technical debt&lt;p&gt;Just remember that technical debt doesn&amp;#x27;t apply to all software.</text></item></parent_chain></comment><story><title>Technical Debt</title><url>https://martinfowler.com/bliki/TechnicalDebt.html</url></story>