Your SlideShare is downloading. ×
Refactoring
Refactoring
Refactoring
Refactoring
Refactoring
Refactoring
Refactoring
Refactoring
Refactoring
Refactoring
Refactoring
Refactoring
Refactoring
Refactoring
Refactoring
Refactoring
Refactoring
Refactoring
Refactoring
Refactoring
Refactoring
Refactoring
Refactoring
Refactoring
Refactoring
Refactoring
Refactoring
Refactoring
Refactoring
Refactoring
Refactoring
Refactoring
Refactoring
Refactoring
Refactoring
Refactoring
Refactoring
Refactoring
Refactoring
Refactoring
Refactoring
Refactoring
Refactoring
Refactoring
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Refactoring

2,331

Published on

Chirag and Aman\'s Refactoring workshop at Agile Mumbai 2008 conference

Chirag and Aman\'s Refactoring workshop at Agile Mumbai 2008 conference

Published in: Technology
0 Comments
11 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
2,331
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
160
Comments
0
Likes
11
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 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
  • 8. Refactoring in Action
  • 9. Code Smells
  • 10. Duplicated Code
  • 11. Long Method
  • 12. Comments
  • 13. Divergent Change
  • 14. Shotgun Surgery
  • 15. Feature Envy
  • 16. Lazy Class
  • 17. Switch Statements
  • 18. Primitive Obsession
  • 19. Method Chains
  • 20. Refactoring Catalog
  • 21. Refactoring Catalog Composing methods
  • 22.  
  • 23.  
  • 24.  
  • 25.  
  • 26.  
  • 27.  
  • 28. Refactoring Catalog Simplifying Conditional Expressions
  • 29.  
  • 30.  
  • 31.  
  • 32.  
  • 33.  
  • 34.  
  • 35.  
  • 36. Refactoring Catalog
    • Making Method Calls Simpler
  • 37.  
  • 38.  
  • 39.  
  • 40.  
  • 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]

×