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

After refactoring some code, make sure your test cases still pass and write new test cases where necessary. Refactoring: Improving the Design of Existing Code, by Fowler et al, Addison-Wesley, 1999. I've long been told that this book is one of the must-reads for developers. After picking it up a few months ago, it took me a while to finish reading it. Here are a few I like: 1) Code Complete 2nd edition by Steve McConnell. Refactoring is about improving the design of existing code. 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. The basic approach involved improving your code's running time by limiting the amount of memory space the program uses. 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. 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”. 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. Refactoring is the process of changing a software system in such a way that it does not alter the external behavior of the code yet improve its internal structure.