Skip to main content
Software Engineering

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.

3
  • 5
    Not so sure. I've been involved in a project recently where we all agree a rewrite would be beneficial.. so we refactored the admin part out, then the DB was re-organised, and soon the main client will get a webby revamp. It'll end up as a huge rewrite with a lot of old code getting reused, but it will continue to work as we make these incremental improvements. I consider this a refactoring even though a lot of new code is being written. I've also been involved in projects, years ago, where a total rewrite was done - nearly bankrupted 2 companies, and didn't deliver the dream anyway. Commented Feb 4, 2014 at 8:28
  • 2
    If the code base is horrible but still being used then gbjbaanb's comments are very valid. Taking bits and making them better whilst keeping the beast rolling along at least keeps the company in business. Re-writes are great for the programmers involved but if it takes two years then it'll be out-dated and redundant before it's even released. Commented Feb 4, 2014 at 16:35
  • 4
    It all comes down to the developers. A total rewrite can work if the developers know exactly what to do and can do it in a practical time scale. Refactoring can also work on the same basis. However I've seen far more code messes created by bad or aborted refactoring because the developers didn't have the time or self discipline. Self discipline is the is the one key factor when refactoring. Too many programmers don't have it. Commented Feb 4, 2014 at 23:28