Sign in with Facebook
Loading...
56th out of 89 books
—
157 voters
Refactoring to Patterns
Kerievsky lays the foundation for maximizing the use of design patterns by helping the reader view them in the context of refactorings. He ties together two of the most popular methods in software engineering today--refactoring and design patterns--as he helps the experienced developer create more robust software.
Hardcover, 400 pages
Published
August 5th 2004
by Addison-Wesley Professional
(first published 2004)
Friend Reviews
To see what your friends thought of this book,
please sign up.
Community Reviews
(showing
1-30
of
759)
Like several other reviewers, this book left me scratching my head slightly and wondering what its aim really was. I was hoping the focus would be more on analysis of legacy code, with advice on discovering and teasing out potential patterns. Instead, this is almost entirely a "how-to" book.
The vast majority of its 350 pages are taken up with 27 refactorings. Each refactoring includes a "how to" section and then an (often lengthy) step-by-step example. Yet, if you're familiar with design pattern...more
The vast majority of its 350 pages are taken up with 27 refactorings. Each refactoring includes a "how to" section and then an (often lengthy) step-by-step example. Yet, if you're familiar with design pattern...more
view 1 comment
This book is an excellent combination of Design Patterns and Refactoring. It's perfect if you're looking to improve your understanding of design patterns and/or refactoring, but it really shines if your goal is to understand how they both work together. Rather than thinking of design patterns as things you cook into your program, which is what usually leads to "design pattern abuse," this book recommends you start with a simple design first, and evolve to design patterns if you start noticing "c...more
Refactoring to Patterns essentially attempts to merge together two types of books: books on code design (such as the GoF Patterns book, Head First Design Patterns, Patterns of Enterprise Application Architecture, etc) and books on engineering principles (such as the eXtreme Programming series and, most of all, Fowler's Refactoring).
In this, it succeeds. Refactoring to Patterns really makes explicit the relationship between agile programming practices and OO design. It draws a connection precisel...more
In this, it succeeds. Refactoring to Patterns really makes explicit the relationship between agile programming practices and OO design. It draws a connection precisel...more
A very good book, balancing the need to present useful refactorings against the risk of alienating readers with too-complicated refactorings. The constant references to Martin Fowler’s work were justified, and if you really want to get the most out of this book, you should have Refactoring and Design Patterns with you.
I didn’t, though, and still found it very interesting. By the end, the “mechanism” section of each refactoring was a little tough slogging, but the examples were very followable. A...more
I didn’t, though, and still found it very interesting. By the end, the “mechanism” section of each refactoring was a little tough slogging, but the examples were very followable. A...more
Oct 10, 2012
Ash Mishra
marked it as to-read
The subject material in this book is what separates those who think they understand the purpose and utilization of patterns, from those who realize that patterns are essential not to just the design of an application, but more importantly to its extensibility and forward maintenance. Too often as software engineers, we have seen two camps of developers: those who are new to the field and unaware of good design, and the latter are those armed and dangerous with knowledge of patterns, but use them...more
Aug 04, 2008
Apple84 Wylie
rated it
3 of 5 stars
Recommended to Apple84 by:
developers involved in large projects or legacy code
In regard to design patterns, lines can be strongly drawn between developers. Some argue it is the only way to code while others believe the practice is sterile and inhibits creativity. I think patterns are useful in some situations and a hinderance in others; for me, their utility factors on a large number of variables, including project type, resources, language, and number of developers involved in the project. It helps to understand and research the technology if only to eschew or discount t...more
Great book about how to refactor code in such a way that it is designed better.
Great and useful book. Highly recommended.
A nice sensible read, with an emphasis on using common sense rather than just blindly following any techniques picked up when learning about patterns.
Recommended!
Recommended!
Very good explanations of each refactoring process that the author undertakes along with code snippets, thought process, steps involved, testing the changes, etc. As a developer you'd want to get into that habit of always refactoring your code to a cleaner / better version.
Great book on the pattern use. Recomended read after the Fowlers refactoring.
Keeping this as a handbook to day-to-day work.
Keeping this as a handbook to day-to-day work.
Provides good insight into assessing need and usage of design patterns.
Jun 16, 2013
Morgan
added it
Jun 14, 2013
Siim Viikman
marked it as to-read
Jun 13, 2013
Henry Suryawirawan
marked it as to-read
Jun 13, 2013
Khaja Ibrahim
marked it as to-read
Jun 12, 2013
Simon Hutchinson
is currently reading it
Jun 09, 2013
Martin Chalupa
marked it as to-read
Jun 09, 2013
Ivaylo
marked it as to-read
Jun 06, 2013
Ryan Svihla
marked it as to-read
Jun 06, 2013
J.R. Garcia
marked it as to-read
Jun 06, 2013
Afriza Noor
marked it as to-read
Jun 05, 2013
Bruno
marked it as to-read
Jun 04, 2013
Eduardo Bobsin
marked it as to-read
There are no discussion topics on this book yet.
Be the first to start one »
