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

€�Refactoring: Improving the Design of Existing Code” is focused on OO programming (lots of Java examples) and Agile practices. Usage of the term increased after it was featured in Refactoring. It is setup as a catalog of refactoring techniques. Refactoring: Improving the Design of Existing Code. Certainly, I just realize how important it becomes when we maintain the code. ̠�자 : 마틴 파울러 옮긴이 : 윤성준, 조재박. Refactoring, I got influence when I read Martin Fowler's book on Refactoring: Improving the Design of Existing Code. Improving the Design of Existing Code. Martin Fowler's discussion book and catalogue of common refactorings is a hugely interesting read. 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. 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. ̛�제 : Refactoring Improving the Design of Existing Code. When you find you have to add a feature to a program, and the program's code is not structured in a convenient way to add the feature, first refactor the program to make it easy to add the feature, then add the feature. ̠�통적인 소프트웨어 개발 단계는 분석-설계-구현-테스트로 이어진다. You may or may not have heard the term Refactoring before, but it is a term that sometimes seems to be used loosely in software development, when someone wants to do something to the code. 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.