Refactoring for Software Design Smells: Managing Technical Debt

I liked the way Technical debt concept was explained. In depth explanation of each object oriented principles and its smells (taking examples from JDK for most of the smells made me understand about each smell in detail since I already knew Java).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!

I have read a lot of material and papers on Technical Debt in hopes of guiding our management that short-cuts will eventually have to be payed for in someway. There is always a cost in developing poorly structured software systems. This book presents a very good explanation of the cost and traps with designs that have deep Technical short comings embedded in it. If I had only one comment to make it would be to drop or replace the word Smells. It is not a good approach to use if you are trying to convince an audience to change strong embedded habits. practical

The thing I enjoyed most about the book is the thorough classification of the discussed topics. It all started with stating different types of technical debts and reasons behind them. Then the description continued with different types of the design smells covering the rationale behind their inclusion in the book, potential causes and many, many examples.

Essential for anyone looking to expand their design and code review skills. I wish more devs would learn this stuff.

I am currently following this book and I must admit that the book is too good.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!

The book itself provides a great and detailed explanation about design smells and the way each one of them can affect the software.I would highly recommend it for reading in both industrial and academic context.

In this book, the complicated design concepts described in very easy way. Classification of design smell is very clear and informative. The explanation flow in each chapter is consistent for easy understanding. Each smell is explained with real examples. The hand-drawn diagrams look nice, powerful and easy to understand. Thank You authors, for the great job.

Refactoring for design smells is an excellent read. It's very comprehensive and covers most of the design smells and importantly, the book goes about its job in a very easy, understandable manner. The writing style along with the examples makes the concepts look simple and more understandable.

I personally found this book to be very useful in furthering my understanding of software design principles and issues that certain design decisions or errors in implementation might cause.It introduces the concept of technical debt and it's probable causes. The book further describes and categorizes various design smells according to the design principles it violates.The subject matter covered provides a detailed vocabulary to understand and communicate design issues.The book also presents methods to refactor and solve these issues. It also has multiple interesting examples on what causes technical debt. All of this is presented in a very easy to read and understandable manner.

its okey

Nice book. Every developer and designer should have this in shelve.

Nice book, people who wants to take coding as seriously it's a good book

I have read this book, it's very nice and useful.