Mon premier blog

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

Pages : 431 ISBN : 0-201-48567-2 Price: $44.95 US Year : 2000 Recently, Refactoring is becoming a hot topic in programming, especially in object oriented programming language. It is setup as a catalog of refactoring techniques. And you can be right saying that I've just read Refactoring: Improving. Fowler, “Refactoring: Improving the Design of Existing Code” location 3320; B. Refactoring: Improving the Design of Existing Code 重構：改善既有程式的設計. Improving the Design of Existing Code. However, in this new paradigm it isn't that design is ignored, but rather, the design This includes major refactoring tasks [11, 10], and helps to support continually improving the design. Guided by Tests” location 1258; M. But good design is critical to the long-term maintainability of code, and generally speaking, developers are taught to deliver large, up-front designs that consider the 'big picture', not just the features being added. ɇ�构的目的是让可以工作的代码更好，使面向对象的代码更简单，更容易维护。书上还说，所有的程序员应当能使用重构技术改进他们的代码。 nuts-and-bolts n.具体细节 前言 Chapter 3. Usage of the term increased after it was featured in 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. Image by seizethedave via Flickr You may say I've been reading a lot recently. Martin, “SRP: The Single Responsibility Principle”, http://www.objectmentor.com/resources/articles/srp.pdf. €�Refactoring: Improving the Design of Existing Code” is focused on OO programming (lots of Java examples) and Agile practices.