Mon premier blog

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. The next book I'll probably get, since I have heard good things about it, is “Refactoring: Improving the Design of Existing Code”. 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. Fowler, “Refactoring: Improving the Design of Existing Code” location 3320; B. Improving the Design of Existing Code (Refactoring). In my short career I have seen entire systems who should have had a major refactoring. This book is all about refactoring. Martin, “SRP: The Single Responsibility Principle”, http://www.objectmentor.com/resources/articles/srp.pdf. While reading the book , I got some impressed tips and mark them as below. Refactoring is the process of changing a software system in such a way that it does not alter the external behavior of the code yet improve its internal structure. This book is an extensive compilation of refactorings that range from providing meaningful names for variable to collapsing class hierarchies. I started with the “Clean Code” book by Robert Martin since I was on a limited budget. Guided by Tests” location 1258; M. Last week, I had the opportunity to do a presentation on refactoring, using Martin Fowler's book Refactoring as the basis, for the Bartlesville Dot Net Users Group (BDNUG).