Refactoring: Improving the Design of Existing Code ebook
Par edwards matthew le vendredi, juillet 14 2017, 18:04 - Lien permanent
Refactoring: Improving the Design of Existing Code by Don Roberts, John Brant, Kent Beck, Martin Fowler, William Opdyke
Refactoring: Improving the Design of Existing Code Don Roberts, John Brant, Kent Beck, Martin Fowler, William Opdyke ebook
Publisher: Addison-Wesley Professional
ISBN: 0201485672, 9780201485677
Page: 468
Format: pdf
It is the process of changing a software system in such a way that it does not alter the external behavior of the code, yet improves its internal structure. Http://www.storytellersoftware.com Mark Mahoney. It was the first I've read related to “clean code”. Chapter 11 Dealing with Generalization（1）Pull Up FieldTwo subclasseshave the same field. What I found most useful are all the examples that are given for almost every refactoring that is described. Usage of the term increased after it was featured in Refactoring: Improving the Design of Existing Code.[1] Code smell is also a term used by agile programmers.[2]. Refactoring: Improving the Design of Existing Code, by Fowler et al, Addison-Wesley, 1999. Image by seizethedave via Flickr You may say I've been reading a lot recently. �Any fool can write code that a computer can understand. It is a great book from Martin Fowler & Co. Refactoring is about improving the design of existing code. It changed the way I am writing code. The basic approach involved improving your code's running time by limiting the amount of memory space the program uses. And you can be right saying that 
I've just read Refactoring: Improving. Move the field to the superclass.（2）Pull Up MethodYou have methodswith identical results on subcl. Also consider reading Martin Fowler's “Refactoring: Improving the Design of Existing Code”. Refactoring: Improving the Design of Existing Code (Martin Fowler, Kent Beck et al.) – The first couple of chapters are a must read for every developer.