Download as PDF, PPTX
Uploaded byRafael Sperling
A better way to learn refactoring
The document discusses refactoring code through examples of code smells like long methods and classes, extracting methods to single responsibilities, eliminating duplicate code through decomposition, and using the FizzBuzz problem to demonstrate refactoring code from an initial implementation to a refactored solution through steps like extracting variables, inverting if statements, extracting methods, and moving code into classes.
A better way to learn refactoring
- 1. A Better WayTo Learn Refactoring @rafael_sperling
- 2.
- 3. ● Long Method ●Large Class ● Primitive Obsession ● Long Parameter List ● DataClumps ● Switch Statements ● Temporary Field ● Refused Bequest ● ... Bad Code Smell Examples @rafael_sperling
- 4. ● Single-Line Statements ●Block Statements ● Methods ● Classes Different Levels of Refactoring @rafael_sperling
- 5. ● Extract methodfor only one responsability ● Eliminate duplication through decomposition ● Allow for decomposition without drawbacks of duplication The Ultimate Goal for Refactoring @rafael_sperling
- 6. ● For everynumber from 0 to 100, ○ If it is divisible by 3, print "Fizz", ○ If it is divisible by 5, print "Buzz", ○ If it is divisible by 3 and 5, print "FizzBuzz" FizzBuzz & The Art of Refactoring @rafael_sperling
- 7.
- 8. @rafael_sperling Eliminate Duplicate WriteLines Calls
- 9. @rafael_sperling Extracted isFuzzi andisBuzzi Variables
- 10.
- 11. @rafael_sperling Extract Display ActualNumber Method
- 12.
- 13. @rafael_sperling Moved FizzBuzz RegionInto Separate Class
- 14.
- 15.