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



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 ebook
Publisher: Addison-Wesley Professional
Page: 468
ISBN: 0201485672, 9780201485677
Format: pdf


Refactoring: Improving the Design of Existing Code (@bookpool) (@amazon) Because all code can be better. Being part of this Don't use design patterns for the sake of design patterns: Good developers love writing crafty, intelligent code. Over the past few months, I've been working with an Agile Team in two-week sprints improving an existing and quite complicated planning environment that my company has been developing over the past few years. ̠�자 : 마틴 파울러 옮긴이 : 윤성준, 조재박. After refactoring some code, make sure your test cases still pass and write new test cases where necessary. Chapter 11 Dealing with Generalization(1)Pull Up FieldTwo subclasseshave the same field. Move the field to the superclass.(2)Pull Up MethodYou have methodswith identical results on subcl. ̠�통적인 소프트웨어 개발 단계는 분석-설계-구현-테스트로 이어진다. ̛�제 : Refactoring Improving the Design of Existing Code. Refactoring: Improving the design of existing code. I think this is the single greatest book on improving software that has ever been written. €�Certain structures in code that suggest (sometimes they scream for) the possibility of refactoring.” Martin Fowler.