Refactoring For Software Design Smells Managing Technical Debit 1 Edition  (English, Paperback, Girish Suryanarayana,Ganesh Samarthyam,Tushar Sharma)

I think this book was a great eye opener for me as it helped me put the problems I encountered in my code into words. This helped me to find reasons for the smells in my application and ways to fix it.

I would recommend this to anyone who wishes to dig deeper into his code and find better ways to address the issues.

Okay

A very well written book that takes reader seamlessly through major design principles and smells that indicate violation of these principles, I liked in particular:

a) Nice categorization of smells according to design principles and how they affect key quality attributes
b) Refactoring techniques for each of the smells and practical considerations before one jumps in for refactoring
c) Potential root causes
d) Interesting anecdotes and case studies that shows what potential problems one cou...

I bought this book and it is really use full in learning design debts. This book is further describes and categorizes various design smells according to the design principles it violates. All design smells are explained with examples. After reading this book I could find some design smells in my application. I could design classes without technical debt as well.
This book is really helpful and I strongly recommend this book for buyers.

The book gives a good categorization of all the design problems you might be having in your code. The categorization of the design problems is done nicely and have been explained in detailed. Each design problem is explained using the design principles violated and possible reasons why the problem might have introduced. It also gives a possible solution to resolve this issue by refactoring your code.

This book i found very useful to improve my vocabulary in software development especially when designing classes. Sometimes i have found issues in the code where people have wrongly abrstraction or encapsulation, but could not find a vocabulary on how to communicate it to the developers so that it is refactored. Now after reading this book i could identify design issues as Imperative abstraction or Unfactored hierarchy etc. and communicate so that it can get refactored.

I also recommend this...

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 presen...