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.

4
  • I bet you will get more up vote if you shorten your steps. Commented May 5, 2011 at 14:37
  • I have to add that most businesses do not budget for this, so refactoring is always too little too late. To manage the increasing entropy of systems is to set up, that from day 1, a budget (10%-20%) is allocated from every job for housekeeping. It's not a bug fix budget. The budget spend is decided by engineering, not management or marketing or sales. It is only used to factor out the entropy created by development, and the spend reduced as the product approaches end of life. Commented May 8, 2011 at 22:26
  • Agreed. Management always want to trim that kind of thing. Sometimes you can get away with hiding it (Add about 20% to the development estimate for doing anything, and when refactoring is needed - DO IT). Commented May 8, 2011 at 23:19
  • 1
    There's a point where you really can't refactor. If you have several disparate business applications that depend on the same lousy interface or database, you can't fix the underlying stuff very well without breaking all of the other apps that depend on the crappy foundation. At this point you really are screwed. Commented May 19, 2011 at 1:33