Refactoring: Improving the Design of Existing Code Don Roberts, John Brant, Kent Beck, Martin Fowler, William Opdyke
Publisher: Addison-Wesley Professional

Refactoring, I got influence when I read Martin Fowler's book on Refactoring: Improving the Design of Existing Code. Certainly, I just realize how important it becomes when we maintain the code. Guided by Tests” location 1258; M. Ever inherit a big mountain of nasty code and have to add new features to it? La semana pasada, para preparar decentemente la charla que impartí en Luce I.T., leí Refactoring: improving the design of existing code de Martin Fowler y Kent Beck. Refactoring - Improving the Design of Existing Code by Martin Fowler, et. Martin, “SRP: The Single Responsibility Principle”, http://www.objectmentor.com/resources/articles/srp.pdf. Fowler, “Refactoring: Improving the Design of Existing Code” location 3320; B. In this post I'll discuss some of the disadvantages of modules, and suggest that Ruby programmers should see them as a method of last resort for code sharing only after carefully considering alternative approaches such as creating classes. As such, it is not a surprise that Refactoring: Improving the Design of Existing Code feels a little dated. However, not as much as I had expected.