- Paperback: 258 pages
- Publisher: Morgan Kaufmann; 1 edition (November 17, 2014)
- Language: English
- ISBN-10: 0128013974
- ISBN-13: 978-0128013977
- Product Dimensions: 7.5 x 0.6 x 9.2 inches
- Shipping Weight: 7.2 ounces (View shipping rates and policies)
- Average Customer Review: 4.8 out of 5 stars See all reviews (7 customer reviews)
- Amazon Best Sellers Rank: #833,770 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Refactoring for Software Design Smells: Managing Technical Debt 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
O'Reilly Learning Series
Featured 'Learning' Series from O'Reilly Media. See more
Frequently bought together
Customers who bought this item also bought
"Given its practical orientation and the variety of real-world examples offered throughout the book, this is a must-have for any practicing software engineer, developer, software architect, or anyone else interested in software design."--Computing Reviews
"... a delightful, engaging, actionable read... you have in your hand a veritable field guide of smells... one of the more interesting and complex expositions of software smells you will ever find... The concept of technical debt is central to understanding the forces that weigh upon systems, for it often explains where and how and why a system is stressed. What delights me about this present book is its focus on technical debt and refactoring as the actionable means to attend to it." --From the foreword by Grady Booch, IBM Fellow and Chief Scientist for Software Engineering, IBM Research
"Evolving software inevitably accumulates technical debt, making maintenance increasingly painful and expensive. The authors, based on their extensive experience, categorize the major design problems (smells) that come up in software, and lucidly explain how these can be solved with appropriate refactoring." --Diomidis Spinellis, Author of “Code Reading and “Code Quality, Addison-Wesley Professional
"...the book I would have loved to write... Refactoring for Software Design Smells is an excellent book. It is another milestone that professionals will use... I’m sure that you will learn a lot from it and that you will enjoy it." --From the foreword by Stéphane Ducasse, Co-author of Object-Oriented Reengineering Patterns, Morgan Kaufmann
From the Back Cover
Refactoring for Software Design Smells presents 25 structural design smells, how they uncover mistakes made while designing, what design principles were overlooked or misapplied, and what principles need to be applied properly to address those smells through refactoring. Organized across common areas of software design, each smell is presented with diagrams and examples illustrating the poor design practices and the problems that result. The authors share insights that have been used to improve refactoring as well as reduce technical debt in software projects. Along the way they recount anecdotes from actual projects on which the relevant smell helped address a design issue.
Browse award-winning titles. See more
If you are a seller for this product, would you like to suggest updates through seller support?
Top Customer Reviews
I like the hand-drawn figures as well. For example, I liked using Smiley to explain Abstraction principle - I felt anyone who is new to OOP also can relate and understand it easily.
Finally the appendix was really useful to evaluate various tools available in market to repay technical debt.
I felt 250 or so pages is not enough for a practical book of this kind - I wanted more!
The simple language, the examples and illustrations, the refactoring suggestions are easy to understand and implement. The case studies and anecdotes given in the book make it more interesting.
The concept of Technical Debt has been nicely explained. The design smells, their classification and details have been presented very well.
The appendix speaks about the tools that can be used for identifying design smells.
Most importantly, the book is very handy and I can carry it all the time with me.
After reading the book, when I analysed my code for design smells, I was surprised with the results :) Code Refactoring is the way to go for sure, but this book gives you a direction for that. I definitely feel benefited with the book. I feel I have been augmented with a better vision altogether.
My recommendation is that every developer should read this book at least once.
Lastly, I thank the esteemed authors who have done a brilliant job of sharing their knowledge in a simple yet very powerful and effective way.
Kudos to you guys and thanks a ton for writing this book!
I would highly recommend it for reading in both industrial and academic context.