RT, this book is to explain the reconstruction of the book, can be said in the industry evaluation is very high, was rated as the classic. Very early to see, but did not read, because of the recent convulsions like suddenly want to read a book, so picked up, a few pages, the publication of personal advice, not to love spray.
A word summarizing---charm, three reconstruction
Slowly refactoring, 1.1-point modification, testing, in modification, in the test.
There is a methodological taste in the book, according to functions, data, inheritance, expression, and several other aspects, the author puts forward some common reconstruction techniques, the book is valuable in that the writer detailed his years of experience, through detailed steps to guide us. Very reference value, is a worthwhile, read-through, and then encounter problems in the search for books.
But, to this day, in reading some of the points raised, inevitably sigh, after all, is more than 10 years ago, with the development of language, IDE progress, the improvement of the overall level of the industry, some views have been reduced to the basic quality, I think, this should be the author advocated, everyone should put the reconstruction on the daily, Everyone should always want to focus on the construction.
Recommended Way of reading:
The first five chapters, one go's reading, will understand how the refactoring is the same thing, the rest of the chapters, you can slowly go to see. You can even wait to see when there is a need, there is no problem. After reading, but also only slightly know the theory, it is not as practical as the real.
There is a lot of comment on this book online, I don't say much here. In short, refactoring is a daily work, not a hammer in the east, a wooden club in the west.
Refactoring-Improving the design of existing code