Refactoring: Improving the Design of Existing Code. Don Roberts, John Brant, Kent Beck, Martin Fowler, William Opdyke

Refactoring: Improving the Design of Existing Code


Refactoring.Improving.the.Design.of.Existing.Code.pdf
ISBN: 0201485672,9780201485677 | 468 pages | 12 Mb


Download Refactoring: Improving the Design of Existing Code



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




This book is all about 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. ̛�제 : Refactoring Improving the Design of Existing Code. ̠�통적인 소프트웨어 개발 단계는 분석-설계-구현-테스트로 이어진다. Way back in 1999 Martin Fowler published Refactoring — Improving the Design of Existing Code. Fowler, “Refactoring: Improving the Design of Existing Code” location 3320; B. I think people see refactoring as a difficult process. Design is hard; so improving design of existing code must be hard, as well, right? In my short career I have seen entire systems who should have had a major refactoring. Refactoring: Improving the Design of Existing Code. Guided by Tests” location 1258; M. 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. Martin, “SRP: The Single Responsibility Principle”, http://www.objectmentor.com/resources/articles/srp.pdf.