Mon premier blog

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 Don Roberts, John Brant, Kent Beck, Martin Fowler, William Opdyke ebook
ISBN: 0201485672, 9780201485677
Page: 468
Format: pdf
Publisher: Addison-Wesley Professional

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. Object oriented development was starting to come into it's own. Being part of this Don't use design patterns for the sake of design patterns: Good developers love writing crafty, intelligent code. Refactoring: Improving the Design of Existing Code. In my career, a very little portion of the projects I was involved with were based on new code. Hence, it is correct and useful to detect clones in the code, but refactoring is not .. 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. Facing an existing project, you sometimes get confronted with “code that smells”. Fowler, Refactoring: Improving the Design of Existing Code, Addison-Wesley Longman, Boston, Ma, USA, 1999. Dating allllll the way back to 1999. After refactoring some code, make sure your test cases still pass and write new test cases where necessary. At the same time, as already suggested by Kapser and Godfrey [5], there are several situations where code duplication seems to be a reasonable or even a beneficial design option. Most of them were based on existing code.