[Refactoringcode] the description of the refactoring book

Last night the book named [Data Structure with Java hubbed] was closed. when talked about the advantage that I have taken of, with the help of that book I familize myself with data structure, especially the Java Collection framework. I think it important for me to further get my position promptation. so today night I prepare to start a new book, whose name is <refactoring: imporve design the existing code> written by Martin Fowler, Kent Beck (contributor ), john Brant (contributor), William

Opdyke, Don Roberts. in the past this book was always talked by friends and was strongrong recommended to me as a primary guigude to Senior Software deverloper. however, for the sake of my laziness, I start to read this book until now.

Refactoring: imporvinmg the design of the existing code shows how Refactoring can make object-oriented code simple and easier to maintain. today refactorign require considerable design know-how, but once tools become availables, all programmers shocould be able to imporve their coding using refactoring techniques.

Early chapters stress the importance of testing in the successful refactoring (when you imporve code, you have to test tot verify that it still works ). after the discuss on how to detect 'smell 'of bad code, readers get to heart of the book, it catalog of over 70 'refactorings' -- tips for better and simpler class design. each tip of is already strated with before and after code.

[Refactoringcode] the description of the refactoring book