<?xml version="1.0" encoding="UTF-8"?>











<rss version="2.0" xmlns:jf="http://www.jivesoftware.com/xmlns/jiveforums/rss">



<channel>
    <title>Support Forums: Message List - Don’t rewrite Your Application</title>
    <link>http://www.theserverside.com</link>
    <description>Most recent forum messages</description>
    <language>en</language>
    
        <generator>Jive Forums Silver 5.5.30 (www.jivesoftware.com)</generator>
    
    <pubDate>Sun, 19 May 2013 03:58:12 -0400</pubDate>


    <item>

        <title>Don’t rewrite Your Application</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=63007</link>

        

        
            <description><![CDATA[<p>The standard link to Joel's "Things You Should Never Do" is missing:</p>...]]></description>
        

        <pubDate>Tue, 27 Sep 2011 07:03:26 -0400</pubDate>

        

        <jf:creationDate>Tue, 27 Sep 2011 07:03:26 -0400</jf:creationDate>
        <jf:modificationDate>Tue, 27 Sep 2011 07:03:26 -0400</jf:modificationDate>
        <jf:date>Sep 27, 2011</jf:date>
        <jf:author>Juergen Weber</jf:author>
        <jf:replyCount>1</jf:replyCount>
    </item>


    <item>

        <title>It depends</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=63007</link>

        

        
            <description><![CDATA[<blockquote>It needs to be evaulated on a case by case basis. Re-write/Re-factor decision is really based on business needs, architecural needs, ROI, level of effort estimates etc.  But as a good coding practice, code needs to be re-factored as often as...]]></description>
        

        <pubDate>Fri, 23 Sep 2011 13:10:05 -0400</pubDate>

        

        <jf:creationDate>Fri, 23 Sep 2011 13:10:05 -0400</jf:creationDate>
        <jf:modificationDate>Fri, 23 Sep 2011 13:10:05 -0400</jf:modificationDate>
        <jf:date>Sep 23, 2011</jf:date>
        <jf:author>Uma Ediga</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>tests</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=63007</link>

        

        
            <description><![CDATA[<p>And don't forget that having good test coverage with regression tests is very helpful with both refactoring and rewriting. If your legacy code is not good for unit tests then functional (black box) tests may help</p>
<p>&nbsp;</p>]]></description>
        

        <pubDate>Fri, 23 Sep 2011 11:29:03 -0400</pubDate>

        

        <jf:creationDate>Fri, 23 Sep 2011 11:29:03 -0400</jf:creationDate>
        <jf:modificationDate>Fri, 23 Sep 2011 11:29:03 -0400</jf:modificationDate>
        <jf:date>Sep 23, 2011</jf:date>
        <jf:author>Bulgar Sadykov</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Fourth reason</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=63007</link>

        

        
            <description><![CDATA[<p>There's actually a fourth reason to refactor rather than rewrite: the legacy codebase almost always contains hidden functionality (features) that can't be found in the documentation. Doing a rewrite will loose these features and will be difficult to...]]></description>
        

        <pubDate>Thu, 22 Sep 2011 06:26:42 -0400</pubDate>

        

        <jf:creationDate>Thu, 22 Sep 2011 06:26:42 -0400</jf:creationDate>
        <jf:modificationDate>Thu, 22 Sep 2011 06:26:42 -0400</jf:modificationDate>
        <jf:date>Sep 22, 2011</jf:date>
        <jf:author>Peter van den Berkmortel</jf:author>
        <jf:replyCount>1</jf:replyCount>
    </item>


    <item>

        <title>Don’t rewrite Your Application</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=63007</link>

        

        
            <description><![CDATA[<p>personally I had several good experiences in taking the rewrite approach. Sure, in two years your code won't be so nice as it was at the beginning, but it is absolutely not the reason to throw away this option. If you stuck with the legacy code, it...]]></description>
        

        <pubDate>Wed, 21 Sep 2011 09:02:30 -0400</pubDate>

        

        <jf:creationDate>Wed, 21 Sep 2011 09:02:30 -0400</jf:creationDate>
        <jf:modificationDate>Wed, 21 Sep 2011 09:02:30 -0400</jf:modificationDate>
        <jf:date>Sep 21, 2011</jf:date>
        <jf:author>Mike J</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Sometimes it's the only way</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=63007</link>

        

        
            <description><![CDATA[<p>What the article fails to explore is that most of the (valid) rewrites of systems or parts of systems are based on incorrect arcitectural decisions taken early on in the original development project. While being neither evil or stupid, people...]]></description>
        

        <pubDate>Wed, 21 Sep 2011 08:19:42 -0400</pubDate>

        

        <jf:creationDate>Wed, 21 Sep 2011 08:19:42 -0400</jf:creationDate>
        <jf:modificationDate>Wed, 21 Sep 2011 08:19:42 -0400</jf:modificationDate>
        <jf:date>Sep 21, 2011</jf:date>
        <jf:author>pellep</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Rewrite decided on several parameters</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=63007</link>

        

        
            <description><![CDATA[<p>Rewriting an Application&nbsp;is decided based on several parameters</p>...]]></description>
        

        <pubDate>Wed, 21 Sep 2011 04:41:58 -0400</pubDate>

        

        <jf:creationDate>Wed, 21 Sep 2011 04:41:58 -0400</jf:creationDate>
        <jf:modificationDate>Wed, 21 Sep 2011 04:41:58 -0400</jf:modificationDate>
        <jf:date>Sep 21, 2011</jf:date>
        <jf:author>Siva Koneru</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Don’t rewrite Your Application</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=63007</link>

        

        
            <description><![CDATA[<p>I'm getting a bit confused about role of a person that article targets. Project sponsor? PM? Architect? Business analyst? Developer?</p>...]]></description>
        

        <pubDate>Tue, 20 Sep 2011 16:01:51 -0400</pubDate>

        

        <jf:creationDate>Tue, 20 Sep 2011 16:01:51 -0400</jf:creationDate>
        <jf:modificationDate>Tue, 20 Sep 2011 16:01:51 -0400</jf:modificationDate>
        <jf:date>Sep 20, 2011</jf:date>
        <jf:author>Pavel Grushetzky</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Don’t rewrite Your Application</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=63007</link>

        

        
            <description><![CDATA[<p>When stuck with a legacy code base you&rsquo;ll hear the claim &ldquo;We&rsquo;ll have to  rewrite this from scratch in order to fix it!&rdquo; It sounds promising. You  start with a clean slate. You can do all the good stuff without all the...]]></description>
        

        <pubDate>Tue, 20 Sep 2011 12:29:32 -0400</pubDate>

        

        <jf:creationDate>Tue, 20 Sep 2011 12:29:32 -0400</jf:creationDate>
        <jf:modificationDate>Tue, 20 Sep 2011 12:29:32 -0400</jf:modificationDate>
        <jf:date>Sep 20, 2011</jf:date>
        <jf:author>Fabrizio Chami</jf:author>
        <jf:replyCount>9</jf:replyCount>
    </item>



</channel>
</rss>

