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

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. Fowler, “Refactoring: Improving the Design of Existing Code” location 3320; B. Guided by Tests” location 1258; M. This book should be treated as a classic in software craftmanship, and its contents are still relevant today as they were in 1999. 3 thoughts on “Refactoring: Improving the Design of Existing Code (Addison-Wesley Object Technology Series)”. 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. Sean Kelly "Consultant" April 27, 2013 at 11:27 am. After refactoring some code, make sure your test cases still pass and write new test cases where necessary. 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. Il est certain que ce livre est une référence sur la pratique du remaniement (Refactoring): L'étude est exhaustive, les patterns de refactoring sont très clairs, les exemples aussi, en java. Martin, “SRP: The Single Responsibility Principle”, http://www.objectmentor.com/resources/articles/srp.pdf. Refactoring: Improving the Design of Existing Code - Martin Fowler.