<story><title>Lessons Learned from Software Rewrites</title><url>http://alexmartins.me/2016/07/28/lessons-learned-from-software-rewrites.html</url></story><parent_chain></parent_chain><comment><author>Terr_</author><text>I&amp;#x27;ve been dealing with a corporate ERP system for some time now, and -- whether rewrite or refactor -- the biggest challenge has been that nobody is willing to assert how it &lt;i&gt;ought&lt;/i&gt; to work.&lt;p&gt;At best, it&amp;#x27;s &amp;quot;reverse engineer it, tell me what it does, and then I&amp;#x27;ll tell you what feature I&amp;#x27;d like changed.&amp;quot;</text></comment>
<story><title>Lessons Learned from Software Rewrites</title><url>http://alexmartins.me/2016/07/28/lessons-learned-from-software-rewrites.html</url></story><parent_chain></parent_chain><comment><author>cottonseed</author><text>When I hear about rewrites, I always think about this comment:&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=11554288&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=11554288&lt;/a&gt;</text></comment>