The Curse Of The Rewrite

Uncle Bob writes about why rewriting an existing Big Ball of Mud is probably the worst thing you can do:

It’s depressing to think that many of the projects I have been brought in on over the past few years were grand rewrites. Technically they have been relatively successful, but probably viewed by the business as time-wasting and expensive. It’s time for this madness to end! Pick up a copy of Michael Feather’s book and start scrubbing!


2 Responses to “The Curse Of The Rewrite”

  1. 1 Mike Wagg January 19, 2009 at 9:13 am

    I’m really starting to think that a lot of this is down to peoples inability to work with legacy code and understanding of how to refactor a mess into something maintainable.

  2. 2 timross January 20, 2009 at 9:59 pm

    @Mike, I think this has a lot to do with being unsure about how to change legacy code without breaking it. Many devs probably think it’s easier just to start again, which is almost never the case! I think there is a lack of knowledge on how to break dependencies and effectively test legacy code, in order to safely refactor and introduce changes.

Leave a Reply

Please log in using one of these methods to post your comment: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: