Refactoring: Improving the Design of Existing

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

Martin, “SRP: The Single Responsibility Principle”, http://www.objectmentor.com/resources/articles/srp.pdf. One of the great books I read about refactoring was, “Refactoring: Improving the Design of Existing Code”, this book is unbelievable, I recommend everyone to read it. Refactoring: Improving the Design of Existing Code. Guided by Tests” location 1258; M. Refactoring enables an approach to design I call reflective design. Also consider reading Martin Fowler's “Refactoring: Improving the Design of Existing Code”. While reading the book , I got some impressed tips and mark them as below. Refactoring: Improving the Design of Existing Code by Martin Fowler, Kent Beck, John Brant, William Opdyke and Don Roberts. As such, it is not a surprise that Refactoring: Improving the Design of Existing Code feels a little dated. Fowler, “Refactoring: Improving the Design of Existing Code” location 3320; B. Design Patterns by Erich Gamma, Richard Helm, Ralph Johnson and John Vlissides. It changed the way I am writing code. Now you can dramatically improve the design, performance, and manageability of object-oriented code without altering its interfaces or behavior. It was the first I've read related to “clean code”. Martin Fowler / Kent Beck / John Brant / William Opdyke / Don Roberts; Publisher: Addison Wesley. In addition to creating a design and coding it, you can now analyze the design of existing code and improve it. However, not as much as I had expected. 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.