<?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 - Refactoring Patterns</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 06:44:49 -0400</pubDate>


    <item>

        <title>Examples will be quite handy</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=37362</link>

        

        
            <description><![CDATA[Good work Santiago.

I guess this will some real examples will be very helpful and will reach the developers in a quick efficient way. 

Also, it is not a bad idea to show UML diagrams before and after refactoring. 

Cheers...
VJ]]></description>
        

        <pubDate>Mon, 22 May 2006 21:14:51 -0400</pubDate>

        

        <jf:creationDate>Mon, 22 May 2006 21:14:51 -0400</jf:creationDate>
        <jf:modificationDate>Mon, 22 May 2006 21:14:51 -0400</jf:modificationDate>
        <jf:date>May 22, 2006</jf:date>
        <jf:author>Vijay Kumar Narayanan</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Refactoring Patterns</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=37362</link>

        

        
            <description><![CDATA[Refactorings like Patterns solve particular problems. Patterns however also model common structures and life cycles amongst types. Refactorings seem to deal heavily in smaller elements than types. (functions or methods where much complex...]]></description>
        

        <pubDate>Thu, 11 May 2006 05:59:13 -0400</pubDate>

        

        <jf:creationDate>Thu, 11 May 2006 05:59:13 -0400</jf:creationDate>
        <jf:modificationDate>Thu, 11 May 2006 05:59:13 -0400</jf:modificationDate>
        <jf:date>May 11, 2006</jf:date>
        <jf:author>John Gagon</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Refactoring Patterns using Eclipse</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=37362</link>

        

        
            <description><![CDATA[Eclipse gives good support for refactoring. You can try<br>this simple method extract functionality in eclipse.<br><br>1. Select few statements within a method, <br>2. Right Click --&gt; Refactor --&gt; ExtractMethod --&gt; Give a <br>method name and...]]></description>
        

        <pubDate>Tue, 21 Mar 2006 05:14:55 -0500</pubDate>

        

        <jf:creationDate>Tue, 21 Mar 2006 05:14:55 -0500</jf:creationDate>
        <jf:modificationDate>Tue, 21 Mar 2006 05:14:55 -0500</jf:modificationDate>
        <jf:date>Mar 21, 2006</jf:date>
        <jf:author>vijay kumar</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Processes rather than Patterns.</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=37362</link>

        

        
            <description><![CDATA[Good general information posted - these are certainly common sense approaches to refactoring. I find myself following the process/patterns described.<br><br>I certainly agree that these are not design patterns yet the material is presented as such.]]></description>
        

        <pubDate>Tue, 27 Dec 2005 00:12:21 -0500</pubDate>

        

        <jf:creationDate>Tue, 27 Dec 2005 00:12:21 -0500</jf:creationDate>
        <jf:modificationDate>Tue, 27 Dec 2005 00:12:21 -0500</jf:modificationDate>
        <jf:date>Dec 27, 2005</jf:date>
        <jf:author>Rohit Sood</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Processes rather than Patterns.</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=37362</link>

        

        
            <description><![CDATA[IMHO what you are calling Patterns here are actually Processes executed before,during and after refactoring. It is a good checklist, but I'm afraid you are trying to fit refactoring activities into the pattern mold. Perhaps you could call them...]]></description>
        

        <pubDate>Tue, 06 Dec 2005 09:43:32 -0500</pubDate>

        

        <jf:creationDate>Tue, 06 Dec 2005 09:43:32 -0500</jf:creationDate>
        <jf:modificationDate>Tue, 06 Dec 2005 09:43:32 -0500</jf:modificationDate>
        <jf:date>Dec 6, 2005</jf:date>
        <jf:author>Ajith Kallambella</jf:author>
        <jf:replyCount>1</jf:replyCount>
    </item>


    <item>

        <title>Any technical comment?</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=37362</link>

        

        
            <description><![CDATA[Any technical comment?]]></description>
        

        <pubDate>Wed, 02 Nov 2005 15:59:12 -0500</pubDate>

        

        <jf:creationDate>Wed, 02 Nov 2005 15:59:12 -0500</jf:creationDate>
        <jf:modificationDate>Wed, 02 Nov 2005 15:59:12 -0500</jf:modificationDate>
        <jf:date>Nov 2, 2005</jf:date>
        <jf:author>Santiago Valdarrama</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>RE: good books for developper point of view</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=37362</link>

        

        
            <description><![CDATA[I agree with you that the best way to make developers learn refactoring is with the form of<br><br>ugly code --&gt; clean code after refactoring<br><br>but my intention isn't instruct developers about the mechanics of refactoring but HOW, WHEN, WHERE and...]]></description>
        

        <pubDate>Mon, 31 Oct 2005 16:38:32 -0500</pubDate>

        

        <jf:creationDate>Mon, 31 Oct 2005 16:38:32 -0500</jf:creationDate>
        <jf:modificationDate>Mon, 31 Oct 2005 16:38:32 -0500</jf:modificationDate>
        <jf:date>Oct 31, 2005</jf:date>
        <jf:author>Santiago Valdarrama</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>good books for developper point of view</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=37362</link>

        

        
            <description><![CDATA[for developpers that have coded like pigs... <br>&nbsp;&nbsp;import java.pigs.*;<br><br>it's hard to make them learn &quot;with patterns&quot; so it's better to start with their &quot;ugly&quot; code and show how it can be improved<br><br>these 2 books...]]></description>
        

        <pubDate>Mon, 31 Oct 2005 13:01:00 -0500</pubDate>

        

        <jf:creationDate>Mon, 31 Oct 2005 13:01:00 -0500</jf:creationDate>
        <jf:modificationDate>Mon, 31 Oct 2005 13:01:00 -0500</jf:modificationDate>
        <jf:date>Oct 31, 2005</jf:date>
        <jf:author>St?phan Mestach</jf:author>
        <jf:replyCount>1</jf:replyCount>
    </item>


    <item>

        <title>Refactoring Patterns</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=37362</link>

        

        
            <description><![CDATA[Well, first of all thanks for consolidating such good information for users on refactoring. I will add my one experience of refactoring to this. In a code when you want to refactor specially flag variables, you need to confirm each and every occurance...]]></description>
        

        <pubDate>Mon, 31 Oct 2005 12:02:54 -0500</pubDate>

        

        <jf:creationDate>Mon, 31 Oct 2005 12:02:54 -0500</jf:creationDate>
        <jf:modificationDate>Mon, 31 Oct 2005 12:02:54 -0500</jf:modificationDate>
        <jf:date>Oct 31, 2005</jf:date>
        <jf:author>Sachin Dharmapurikar</jf:author>
        <jf:replyCount>2</jf:replyCount>
    </item>


    <item>

        <title>Refactoring Patterns</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=37362</link>

        

        
            <description><![CDATA[The following URLs contains some patterns that are members of a more complex pattern language. The goal of these patterns is to help people to understand HOW to refactor their programs.<br><br>These patterns were already published in two seminars and one...]]></description>
        

        <pubDate>Mon, 31 Oct 2005 00:31:48 -0500</pubDate>

        

        <jf:creationDate>Mon, 31 Oct 2005 00:31:48 -0500</jf:creationDate>
        <jf:modificationDate>Mon, 31 Oct 2005 00:31:48 -0500</jf:modificationDate>
        <jf:date>Oct 31, 2005</jf:date>
        <jf:author>Santiago Valdarrama</jf:author>
        <jf:replyCount>9</jf:replyCount>
    </item>



</channel>
</rss>

