I sure hope that we don't dismiss the reading of such books just because "every experienced programmer knows about refactoring".
-- Sriram On 12/6/10, Siddharta G <siddharta.li...@gmail.com> wrote: > Nice quote. > > You hit the main point: Refactoring has always been done. Everyone does it. > The book just gives a taxonomy to common refactorings. > > For what its worth, I think a taxonomy is very important. It is so much > easier to communicate a design by saying this is a factory, that object is > an observer to the model and so on. The same way its convenient to say first > extract method, then pull up method and everyone understands what you are > talking about. > > But whether you know the names or not, it is important to know how to go > from design A to design B in small steps, without breaking the application > in between. A typical refactoring step takes less than an hour (some can be > as low as a few minutes). You can do a refactoring, commit, do a > refactoring, commit and the application is always deployable. > > -- Siddharta > _______________________________________________ > BangPypers mailing list > BangPypers@python.org > http://mail.python.org/mailman/listinfo/bangpypers > -- Sent from my mobile device ================== Belenix: www.belenix.org _______________________________________________ BangPypers mailing list BangPypers@python.org http://mail.python.org/mailman/listinfo/bangpypers
