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



Refactoring: Improving the Design of Existing Code pdf download




Refactoring: Improving the Design of Existing Code Don Roberts, John Brant, Kent Beck, Martin Fowler, William Opdyke ebook
ISBN: 0201485672, 9780201485677
Format: pdf
Publisher: Addison-Wesley Professional
Page: 468


El título me pareció sugerente. Being part of this Don't use design patterns for the sake of design patterns: Good developers love writing crafty, intelligent code. After refactoring some code, make sure your test cases still pass and write new test cases where necessary. Martin Fowler, Kent Beck, John Brant, William Opdyke, Don Roberts. 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: Improving the Design of Existing Code, by Fowler et al, Addison-Wesley, 1999. Http://www.storytellersoftware.com Mark Mahoney. Object oriented development was starting to come into it's own. The basic approach involved improving your code's running time by limiting the amount of memory space the program uses. Usage of the term increased after it was featured in Refactoring: Improving the Design of Existing Code.[1] Code smell is also a term used by agile programmers.[2]. Refactoring: improving the design of existing code. Dating allllll the way back to 1999. Refactoring: Improving the Design of Existing Code.