Anand Balachandran Pillai
abpillai at gmail.com
Sun Dec 5 12:49:34 CET 2010
On Sun, Dec 5, 2010 at 4:53 PM, Siddharta G <siddharta.lists at gmail.com>wrote:
> On Sun, Dec 5, 2010 at 4:07 PM, Anand Balachandran Pillai <
> abpillai at gmail.com> wrote:
> > That is re-architecting or re-designing depending on which side of the
> > conference table you are - not re-factoring.
> Err... Refactoring _is_ redesigning, that is the whole purpose of
> The difference is that traditional rearchitecting/redesiging is taking down
> the existing design and rewriting the application with a new design.
> Refactoring is doing it in such a way that you can go from A -> B in small
> steps without breaking the app at any point.
I understand the difference. You mentioned "Architecture changes"
which doesn't belong to re-factoring.
In a way, the whole "re-writing vs re-factoring" thing is a bit blown-up
since the answer to the most important question "Who throws away
an entire piece of code and re-writes it from scratch" is "Not many",
unless the code is highly experimental, a prototype, is a personal
project (with not many users), or has hit the critical limit of usability
extensibility in its current state, so that it has to be re-written from
So, most of us do "re-factoring" or "whatever you may want to call it",
almost routinely, whether it is at a code, design or architectural level.
> BangPypers mailing list
> BangPypers at python.org
More information about the BangPypers