Refactoring for Software Design Smells: Managing Technical Debt,Used
Refactoring for Software Design Smells: Managing Technical Debt,Used
Refactoring for Software Design Smells: Managing Technical Debt,Used
Refactoring for Software Design Smells: Managing Technical Debt,Used
Refactoring for Software Design Smells: Managing Technical Debt,Used

Refactoring for Software Design Smells: Managing Technical Debt,Used

In Stock
SKU: SONG0128013974
Brand: Morgan Kaufmann
Regular price$10.67
Quantity
Add to wishlist
Add to compare

Processing time: 1-3 days

US Orders Ships in: 3-5 days

International Orders Ships in: 8-12 days

Return Policy: 15-days return on defective items

Payment Option
Payment Methods

Help

If you have any questions, you are always welcome to contact us. We'll get back to you as soon as possible, withing 24 hours on weekdays.

Customer service

All questions about your order, return and delivery must be sent to our customer service team by e-mail at yourstore@yourdomain.com

Sale & Press

If you are interested in selling our products, need more information about our brand or wish to make a collaboration, please contact us at press@yourdomain.com

Awareness of design smells indicators of common design problems helps developers or software engineers understand 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. Developers and software engineers may "know" principles and patterns, but are not aware of the "smells" that exist in their design because of wrong or misapplication of principles or patterns. These smells tend to contribute heavily to technical debt further time owed to fix projects thought to be complete and need to be addressed via proper refactoring.Refactoring for Software Design Smells presents 25 structural design smells, their role in identifying design issues, and potential refactoring solutions. 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, creating a catalog of nuggets of readily usable information that developers or engineers can apply in their projects. The authors distill their research and experience as consultants and trainers, providing insights that have been used to improve refactoring and reduce the time and costs of managing software projects. Along the way they recount anecdotes from actual projects on which the relevant smell helped address a design issue. Contains a comprehensive catalog of 25 structural design smells (organized around four fundamental designprinciples) that contribute to technical debt in software projects Presents a unique naming scheme for smells that helps understand the cause of a smell as well as pointstoward its potential refactoring Includes illustrative examples that showcase the poor design practices underlying a smell and the problemsthat result Covers pragmatic techniques for refactoring design smells to manage technical debt and to create and maintainhighquality software in practice Presents insightful anecdotes and case studies drawn from the trenches of realworld projects

⚠️ WARNING (California Proposition 65):

This product may contain chemicals known to the State of California to cause cancer, birth defects, or other reproductive harm.

For more information, please visit www.P65Warnings.ca.gov.

Recently Viewed