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 eBook




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


Refactoring improving the design of existing code[ebook]. After refactoring some code, make sure your test cases still pass and write new test cases where necessary. Martin, “SRP: The Single Responsibility Principle”, http://www.objectmentor.com/resources/articles/srp.pdf. 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. The term “code smell” is attributed to Kent Beck in Martin Fowler's book Refactoring, Improving the Design of Existing Code (Addison-Wesley, 1999, ISBN 0-201-48567-2). Refactoring: Improving the Design of Existing Code Martin Fowler with Kent Beck, John Brant, William Opdyke and Don Roberts. Refactoring: Improving the Design of Existing Code. Fowler, “Refactoring: Improving the Design of Existing Code” location 3320; B. The basic approach involved improving your code's running time by limiting the amount of memory space the program uses. Guided by Tests” location 1258; M. Being part of this Don't use design patterns for the sake of design patterns: Good developers love writing crafty, intelligent code. In this post I'll discuss some of the disadvantages of modules, and suggest that Ruby programmers should see them as a method of last resort for code sharing only after carefully considering alternative approaches such as creating classes. Refactoring: Improving the Design of Existing Code, by Fowler et al, Addison-Wesley, 1999. In the Addison-Wesley Object Technology Series.