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

Refactoring: Improving the Design of Existing Code. In my short career I have seen entire systems who should have had a major refactoring. 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. Refactoring: Improving the Design of Existing Code; Design Patterns, Gang of Four; Test Driven Development: By Example; The Art of Unit Testing: With Examples in .NET. Martin, “SRP: The Single Responsibility Principle”, http://www.objectmentor.com/resources/articles/srp.pdf. Once upon a time, a consultant made a visit to a development project. Preface from the book 'Refactoring: Improving the Design of Existing Code'. Fowler, “Refactoring: Improving the Design of Existing Code” location 3320; B. Fowler, Martin, Brant, John, Opdyke, William and Roberts, Don (1999): Refactoring: Improving the Design of Existing Code. (ed.) (2001): Human-Computer Interaction in the New Millennium. This book is all about refactoring. Guided by Tests” location 1258; M. I got curious and downloaded its Eclipse plugin, I then picked the first bad smell code which Martin Fowler explains in his book: “Refactoring: Improving the design of existing code”.