Code smells & Refactoring

Code smells are certain lines in the code that indicate a violation of fundamental design principles and negatively impact design quality. We will be discussing different types of code smells and refactoring techniques to remove those smells.

Transcript

1. Code smell & Refactoring Mamata Gelanee
2. Code Smell are certain structures in the code that indicate violation of fundamental design principles and negatively impact design quality. Refactoring is a disciplined technique for restructuring an existing body of code, altering its internal structure without changing its external behavior.
3. “A code smell is a surface indication that usually corresponds to a deeper problem in the system” - Martin Flower
4. Design Principles Every OO Designer should have follow below design principle, failing to that leads to code smells in your software. Design Principles: - Single Responsibility - Open Close principle - Interface Segregation - Dependency Inversion principle - Liskov Substitution principle
5. Levels of Code smell There are three levels of code smell: 1. Method level 2. Class level 3. Application level
6. Bad smells in a code Long Method - Extract method Long class - Extract Class Long parameter list - Introduce Object parameter Primitive Obsession - Introduce Object parameter Duplicate Code (Don’t Repeat Yourself) - Create Template method
7. Long Parameter List
8. Primitive Obsession
9. Duplicate code
10. Switch statements Replace conditional with polymorphism
11. Oddball Solution Move method or Move class
12. Black sheep Move Method
13. Refused Bequest 1. Throw exceptions 2. Push down method or field
14. Speculative Generality Oh! We might need this feature in future Remedy: - Collapse Hierarchy - Inline class - Remove Parameter
15. Quiz Long class
16. Quiz Long Parameter list
17. Questions?
18. Thanks! Software Engineer, Mastercard Transaction solution pvt. Ltd., Vadodara - Gujarat AndiGeeky @MamataGelanee andigeeky.wordpress.com/ mamatagelanee07