Mon premier blog

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

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. Also consider reading Martin Fowler's “Refactoring: Improving the Design of Existing Code”. 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). Fowler, “Refactoring: Improving the Design of Existing Code” location 3320; B. Now you can dramatically improve the design, performance, and manageability of object-oriented code without altering its interfaces or behavior. 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”. It changed the way I am writing code. Improving the Design of Existing Code (Refactoring). Martin, “SRP: The Single Responsibility Principle”, http://www.objectmentor.com/resources/articles/srp.pdf. 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. It was the first I've read related to “clean code”.