Loading ...
Sorry, an error occurred while loading the content.

Re: [XP] When to refactor?

Expand Messages
  • J. B. Rainsberger
    ... How exactly did the code get up to snuff in the first place? Surely we refactored, even without knowing the next story. -- J. B. (Joe) Rainsberger Diaspar
    Message 1 of 24 , Sep 1, 2005
    • 0 Attachment
      yahoogroups@... wrote:

      >>I wonder about this. If our codebase isn't well-factored, then how can
      >>we claim to keep the cost of change low? Part of the evolutionary design
      >>pitch is "We don't prepare for any particular kind of change; we can
      >>handle any kind of change without prohibitive expense." If we tend to
      >>refactor only in the presence of the next story, then how can that
      >>statement be true?
      >
      > I see that in the presence of legacy code. You don't stop and rewrite
      > the whole code base, you clean up the parts you have to work on.
      >
      > If your code is currently up to snuff, then why would you want to
      > refactor except when you're changing it, that is, in the presence of
      > a story?

      How exactly did the code get up to snuff in the first place? Surely we
      refactored, even without knowing the next story.
      --
      J. B. (Joe) Rainsberger
      Diaspar Software Services
      http://www.diasparsoftware.com
      2005 Gordon Pask Award Winner for contribution to Agile practice
      Author, JUnit Recipes: Practical Methods for Programmer Testing
    Your message has been successfully submitted and would be delivered to recipients shortly.