Refactoring
Download as PPT, PDF11 likes903 views
Refactoring is a technique to clean up and improve the design of existing code without changing its external behavior. It involves simplifying code by removing duplicate code, extracting logic into well-named methods and variables, and restructuring code to make it more readable and maintainable. The document recommends practicing small refactorings, using refactoring tools in IDEs, and pairing refactoring with test-driven development to improve code quality over time without introducing bugs.
![Thank You Aman King [email_address] Chirag Doshi [email_address]](https://image.slidesharecdn.com/refactoring-1208260973972457-9/85/Refactoring-44-320.jpg)
Refactoring
- 1. Refactoring Aman & Chirag ThoughtWorks Pune
- 2. If it ain’t broken, why fix it?
- 3. Good programmers write code that humans can understand
- 4. You write code once; it gets read many times
- 5. To regain control on a program that is getting out of hands
- 6. To make the next change easier
- 7. This brings us to Refactoring
- 9. Code Smells
- 10. Duplicated Code
- 11. Long Method
- 12. Comments
- 13. Divergent Change
- 14. Shotgun Surgery
- 15. Feature Envy
- 16. Lazy Class
- 19. Method Chains
- 21. Refactoring Catalog Composing methods
- 28. Refactoring Catalog Simplifying Conditional Expressions
- 36. Refactoring Catalog Making Method Calls Simpler
- 41. Accompanying XP Practices TDD : “Red - Green - Refactor” mantra Continuous Integration Collective Code Ownership Pair Programming
- 42. Next steps for you Go read the book!!! Practice small refactorings Explore the “Refactor” menu of your IDE Keep a look out for code smells in your project
- 43. To sum it up… Refactoring is a good technique to clean up code Refactoring leads to better design (especially with Test-Code-Refactor cycles) Most important of all: it leaves a nice feeling at the end of it all!
- 44. Thank You Aman King [email_address] Chirag Doshi [email_address]