Refactoring Ruby Edition

Slides based on the book: "Refactoring: Ruby Edition"

Transcript

1. Refactoring Rubylit Edition @julioalucero
2. An Example
3. An Example
5. “A change made of the internal structure of software to make it easier to understand and cheaper to modify without changing its observable behavior”
6. THE TWO HATS
7. WHY SHOULD YOU REFACTOR? • Mejora el diseño del software • Hace que el software sea más fácil de entender • Ayuda a encontrar errores • Ayuda a Programar más Rápido
8. BAD SMELLS IN CODE
9. THE VALUES OF THE TESTS
10. Kinds of Refactorings 1. Composing Methods 2. Moving Features Between Objects 3. Organization Data 4. Simplifying Conditional Expressions 5. Making Method Calls Simpler 6. Dealing with Generalization
11. 1. COMPOSING METHODS
12. 2. MOVING FEATURES BETWEEN OBJECTS
13. 2. MOVING FEATURES BETWEEN OBJECTS
14. 3. Organization Data row = [ ] row[0] = "Bichi Gol" row[1] = "20" # refactoring row = Player.new row.name = "Bichi Gol" row.goals = "20" Replace Array with Object
15. 4. Simplifying Conditionals Expressions
16. 4. Simplifying Conditionals Expressions
17. 4. Simplifying Conditionals Expressions
18. 5. MAKING METHOD CALLS SIMPLER
19. 6. DEALING WITH GENERALIZATION • Pull Up/Down Method • Extract Module • Extract Subclass • Introduce Inheritance
20. 6. DEALING WITH GENERALIZATION
21. 6. DEALING WITH GENERALIZATION
22. Guarda que termina. • Solid suite of test. • Always in small steps. • Any fool can write code that a computer can understand. Good programmers write code that humans can understand.
23. ESTE ES EL FINAL