The document discusses refactoring code to improve quality and maintainability. It defines code smells as structures in code that indicate refactoring is needed, like long methods, large classes, duplicate code, and comments. It explains benefits of refactoring like improved readability, reduced bugs, and easier programming. Common refactoring techniques are described like moving features between objects and simplifying conditional expressions. Different types of code smells are also defined like bloated code, change preventers, and couplers.

2. RADU VUNVULEA MCTS MCP BANK HOME AUTOMATION
MVP ENTERPRISE
AUTOMOTIVE PHARMA
LEAN AND AGILE E-COMMERCE
WEB iQuest
AZURE JAVASCRIPT VUNVULEARADU.BLOGSPOT.COM
MOBILE DOTNET @RaduVunvulea
WCF WPF ENTHUSIASTIC

7. Add new functionality
Optimize performance

8. Simplify code
Improve code readibility

9. Reduce
duplication
Make code
clear
Improve
maintainability
Help to find
bugs
Help to
program faster
Fix design
Improve code
quality
Code Smells

10. You do something
the first time
You do similar thing
again with regret
On the third time -
START refactoring

12. • Prepare code
• Understand the code
Adding new
functionality
• Error is a sign of refactoring
• Understand the code
Bug fixing
• Code reviewCode review
When

14. “smells are certain
structures in the code that
suggest (scream for) the
possibility of refactoring”

15. Signs of a low quality code
Code is working, but something is fishy
Each time we need to make a change in 4 places
Nobody understand that code

17. • Fragile
• Rigid
• Complex
• Repetitive
Design Smell
• Reusability
• Changeability
• Extensibility
Design Quality
• Maintainability
• Reliability
Product
Quality

18. Rewrite Refactor

19. Edit and
Pray
Cover and
Modify

20. Composing Methods
Moving Features Between Objects
Organizing Data
Simplifying Conditional Expressions
Making Method Calls Simpler
Dealing with Generalization

22. Bloaters
Object-Orientation Abusers
Change Preventers
Dispensables
Couplers

23. Bloater
Obje
Cha
Disp
Couple

24. Large class
Primitive Obsession
Long Parameter List
Data Clumps
Bloater
Obje
Cha
Disp
Couple

25. Long method
Primitive Obsession
Long Parameter List
Data Clumps
Bloater
Obje
Cha
Disp
Couple

26. Long method
Large class
Long Parameter List
Data Clumps
Bloater
Obje
Cha
Disp
Couple

27. Long method
Large class
Primitive Obsession
Data Clumps
Bloater
Obje
Cha
Disp
Couple

28. Long method
Large class
Primitive Obsession
Long Parameter List
Bloater
Obje
Cha
Disp
Couple

29. Refused Bequest*
Bloater
Obje
Cha
Disp
Couple

30. Temporary Field
Refused Bequest*
Alternative Classes with Different
Interfaces
Bloater
Obje
Cha
Disp
Couple

31. Switch Statements
Refused Bequest*
Alternative Classes with Different
Interfaces
Bloater
Obje
Cha
Disp
Couple

32. Switch Statements
Temporary Field
Refused Bequest*
Bloater
Obje
Cha
Disp
Couple

33. Bloater
Obje
Cha
Disp
Couple

34. Divergent Change Bloater
Obje
Cha
Disp
Couple

35. Divergent Change
Parallel Inheritance Hierarchies
Bloater
Obje
Cha
Disp
Couple

36. Divergent Change
Shotgun Surgery
Bloater
Obje
Cha
Disp
Couple

37. Lazy Class*
Bloater
Obje
Cha
Disp
Couple

38. Duplicate Code
Lazy Class*
Data Class
Dead Code
Speculative Generality
Bloater
Obje
Cha
Disp
Couple

39. Comments
Lazy Class*
Data Class
Dead Code
Speculative Generality
Bloater
Obje
Cha
Disp
Couple

40. Comments
Duplicate Code
Lazy Class*
Dead Code
Speculative Generality
Bloater
Obje
Cha
Disp
Couple

41. Comments
Duplicate Code
Lazy Class*
Data Class
Speculative Generality
Bloater
Obje
Cha
Disp
Couple

42. Comments
Duplicate Code
Lazy Class*
Data Class
Dead Code
Bloater
Obje
Cha
Disp
Couple

43. *Feature Envy
*Inappropriate Intimacy
*Message Chains
*Middle Man (this should be presented)
*Incomplete Library Class
Bloater
Obje
Cha
Disp
Couple

46. Question
Answers

47. {
“name” : “Radu Vunvulea,
“blog” : “vunvulearadu.blogspot.com”,
“email” : ”vunvulear@outlook.com”,
“socialMedia” :
{
“twitter” : “@RaduVunvulea”,
“fb” : “radu.vunvulea”
}
}

48. Today: Enjoy the day
Tonight: Take a look on
https://sourcemaking.com/ refactoring

49. {
“name” : “Radu Vunvulea,
“blog” : “vunvulearadu.blogspot.com”,
“email” : ”vunvulear@outlook.com”,
“socialMedia” :
{
“twitter” : “@RaduVunvulea”,
“fb” : “radu.vunvulea”
}
}