News for hackers. Stuff that matters.
Re:Independent Refactoring is Irresponsible by mratzloff on Friday February 01, 2013 @09:38AM (#5150875)
Refactoring as a separate task is a bad idea from good intentions. If you blow your schedule on some other higher-priority tasks (i.e., directly business-relevant), guess which task is the top candidate for deferral? Speaking from experience.

Paying down technical debt is business-relevant, but not directly relevant. That means things on fire or new contracts or whatever will always supersede things of indirect benefit. Under sufficient load, this effectively means no refactoring, because people are then trained to wait until they are tasked with "the refactoring task".

What has served me well is following Fowler's advice, which is repeated in this article. Refactor when you want to do something else. I would add: Prefer modifying only code that will be QA tested anyway, so you don't explode your testing surface area. Do it as part of a directly business-relevant task. Build it into your estimates.

Re:Independent Refactoring is Irresponsible by gambler on Friday February 01, 2013 @12:40PM (#5152135)
How would you approach, say, encapsulating a global static field that's used in every single file of a legacy application using Fowler's advise?
Re:Independent Refactoring is Irresponsible by mratzloff on Friday February 01, 2013 @01:09PM (#5152310)
I wouldn't, unless it's hampering you from doing something else OR you've got a full regression test coming up (for example, during a major version increment).