Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

2
  • I think this answer addresses the key points of the question best :) Could you also elaborate on the importance of safe refactoring and reverse-engineering for agile development? I was assuming it played a very important role? Maybe it's less than I thought and tools for dynamics language are just good enough. Commented Sep 27, 2012 at 21:09
  • 1
    @Gerenuk - I do not have sufficient experience with agile development (esp. in dynamic languages) to give an authoritative answer--is the refactoring aspect de-emphasized, left the same, etc.? Keep in mind that other common aspects of the process--test-driven development, for example--can help pinpoint where your refactoring went awry, and if you put a little more effort into, say, the design phase, you may not need to refactor as much. I don't think one particular technique is the key--it's keeping a full set of tools at hand, deployed frequently and collaboratively. Commented Sep 27, 2012 at 21:31