Mon premier blog

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

When I first read Refactoring, I believed that tests were a necessary prerequisite before making structural changes to the code. Refactoring: Improving the Design of Existing Code; Design Patterns, Gang of Four; Test Driven Development: By Example; The Art of Unit Testing: With Examples in .NET. I got curious and downloaded its Eclipse plugin, I then picked the first bad smell code which Martin Fowler explains in his book: “Refactoring: Improving the design of existing code”. Hence, it is correct and useful to detect clones in the code, but refactoring is not .. However, not as much as I had expected. As such, it is not a surprise that Refactoring: Improving the Design of Existing Code feels a little dated. Fowler, Refactoring: Improving the Design of Existing Code, Addison-Wesley Longman, Boston, Ma, USA, 1999. It is the process of changing a software system in such a way that it does not alter the external behavior of the code, yet improves its internal structure. My experience is that refactoring is a big ait to building software quickly. (Refactoring: Improving the Design of Existing Code, Fowler et al, 1999). Software developers are professionals. Refactoring is about improving the design of existing code. Our job is to build effective software as rapidly as we can. The first place prize will be a copy of Refactoring: Improving The Design Of Existing Code, an Ubuntu Mug, an Ubuntu 10.04 LTS install disc, and a Mun pen. 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.