Beefy Boxes and Bandwidth Generously Provided by pair Networks
Pathologically Eclectic Rubbish Lister

Re: OT: Rewrite or Refactor?

by dws (Chancellor)
on Aug 27, 2006 at 05:32 UTC ( #569861=note: print w/replies, xml ) Need Help??

in reply to OT: Rewrite or Refactor?

Less likely to miss functionalities from the old code base.

Indeed. In any large code base that's grown up over a period long enough for the original developers to have moved on, there are going to be chunks of essential functionality that aren't well understood. When you rewrite (and miss the misunderstood functionality), you're forced into reactive rediscovery under fire when something that people depend on suddenly no longer works. Not a fun place to be.

Joel Spolsky had a post a while back called Things You Should Never Do, wherein he claims that rewriting working software is a huge mistake. He lays out some good arguments.

If you choose to go the refactoring route, Michael Feathers book Working Effectively with Legacy Code might provide you with some good tools. He tackles the problem of how you retrofit tests onto legacy code in preparation for adding new features (which often involves first making the code safe to refactor).

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://569861]
[LanX]: obscure facts: only naturally born monks can become president here!
[cbeckley]: I have a functioning module I use to spawn sets of commands across multiple servers.
[cbeckley]: It's nascent, and probably looks like baby Perl to the veterans.
[cbeckley]: I have several questions about it's future development. But it seems like a lot of code to put in a sopw.

How do I use this? | Other CB clients
Other Users?
Others perusing the Monastery: (12)
As of 2017-03-24 14:56 GMT
Find Nodes?
    Voting Booth?
    Should Pluto Get Its Planethood Back?

    Results (304 votes). Check out past polls.