This blog post is part of a series about legacy coderetreat<\/a> and legacy code techniques you can apply during your work. Please click to see more sessions<\/a> about legacy code.<\/p>\n This is a code cast in Java.<\/p>\n When refactoring legacy code we need to make sure the structures we extract have a correct meaning. This is why The Rule of Three is very useful: extract to a new structure only when you find an identical duplication three times. Usually we do not have identical duplication, so in that case we need to make the duplication clear, check that it exists three times and only after that perform the extraction.<\/p>\n This code cast will show you also when it is not a good idea to extract a new variable, even if you see it duplicated many times. This is a mechanical kind of refactoring, but reasoning is very important even when we want to get fast by getting mechanical refactorings into our tool bag.<\/p>\n Read here<\/a> more about this concept in my blog post.<\/p>\nCode Cast<\/h3>\n
\n