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

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” is focused on OO programming (lots of Java examples) and Agile practices. Refactoring: Improving the Design of Existing Code (@bookpool) (@amazon) Because all code can be better. By far the most important programming book I ever read was Martin Fowler's "Refactoring: Improving the Design of Existing Code". The concept of 'Code smells' was popularized by Kent Beck and Martin Fowler in the book 'Refactoring: Improving the Design of Existing Code' (ISBN 978-0201485677). Refactoring enables an approach to design I call reflective design. Martin, “SRP: The Single Responsibility Principle”, http://www.objectmentor.com/resources/articles/srp.pdf. Beck, “Refactoring: improving the design of existing code”, Addison Wesley Longman, 1999, pp.238 – 240. Guided by Tests” location 1258; M. Fowler, “Refactoring: Improving the Design of Existing Code” location 3320; B. Michael Wooten replied on Mon, 2011/10/31 - 12:29pm. I think this is the single greatest book on improving software that has ever been written. It is setup as a catalog of refactoring techniques. In addition to creating a design and coding it, you can now analyze the design of existing code and improve it. 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”. Refactoring: Improving the Design of Existing Code - Martin Fowler. This book should be treated as a classic in software craftmanship, and its contents are still relevant today as they were in 1999.