Refactoring: Improving the Design of Existing Code. 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
ISBN: 0201485672,9780201485677 | 468 pages | 12 Mb




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




The basic approach involved improving your code's running time by limiting the amount of memory space the program uses. After refactoring some code, make sure your test cases still pass and write new test cases where necessary. Final Thoughts Refactoring Helps You Find Bugs . Preface from the 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. Once upon a time, a consultant made a visit to a development project. 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 Replacing the Conditional Logic on Price Code with Polymorphism . Refactoring: Improving the Design of Existing Code. One of the great books I read about refactoring was, “Refactoring: Improving the Design of Existing Code”, this book is unbelievable, I recommend everyone to read it. Refactoring: Improving the Design of Existing Code (Martin Fowler, Kent Beck et al.) – The first couple of chapters are a must read for every developer. Refactoring: Improving the Design of Existing Code, by Fowler et al, Addison-Wesley, 1999. Where Did Refactoring Come From?