Beefy Boxes and Bandwidth Generously Provided by pair Networks
laziness, impatience, and hubris
 
PerlMonks  

Re: OT: Rewrite or Refactor?

by adrianh (Chancellor)
on Aug 27, 2006 at 09:27 UTC ( #569870=note: print w/replies, xml ) Need Help??


in reply to OT: Rewrite or Refactor?

My vote would be for refactor. Two reasons. You've missed on big disadvantage from the rewrite option. You won't have a working system for some time. If you're refactoring you'll always have a working system.

We might not end up with the new ideal architecture, because refactoring works on the code level, not on architectural level.

I think you will get your ideal architecture, or at least you can get there with some tiny rewrites on top of a lot of refactoring. That's been my experience anyway. The architecture is, after all, embodied in the code. In general I've found incremental change to be a far more effective technique that a rewrite from scratch.

Take a look at Working Effectively with Legacy Code and the Strangler Application pattern for some ideas.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://569870]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others meditating upon the Monastery: (8)
As of 2020-10-19 15:26 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    My favourite web site is:












    Results (204 votes). Check out past polls.

    Notices?