Refactoring is different than clean-up. When cleaning I care about Clean Code, Coding Standards, Clarity, etc. Refactoring is difficult to make when I don’t have Coding Standards, because the duplication is more difficult to spot.<\/p>\n
Every once in a while clean-up the code so that you can refactor your design easier!<\/p><\/blockquote>\n
Refactoring<\/h2>\n
The refactoring approach during this episode is mainly focused on design. There are many reasons to do refactoring: improve clarity, design, minimize defects, exploring alternatives, etc. These are the final stages in the TDD as if you Meant It cycle, when the design elements are almost ready to be separated completely from the tests.<\/p>\n
Clean-Up<\/h2>\n
Cleaning up is important every once in a while. Without a clean code we cannot focus on the essentials, because there is too much mess. By clean-up I mean deleting the unused methods, delete the useless comments that initially were important, having the same structure in the same place, etc.<\/p>\n
I really like having classes look the same: constants at the top, fields, constructor, public methods, private methods. And also having always the same spacing between methods, parameters, etc. All these have to do with the coding standards I use.<\/p>\n
Coding standards are useful because they let me focus on what I need to refactor. I can easier see duplication between classes if they are structured the same.<\/p>\n
Video<\/h2>\n
Check the video below with the codecast:<\/p>\n