{"id":1627,"date":"2015-04-27T13:36:34","date_gmt":"2015-04-27T10:36:34","guid":{"rendered":"http:\/\/blog.adrianbolboaca.ro\/?p=1627"},"modified":"2020-01-15T22:07:12","modified_gmt":"2020-01-15T20:07:12","slug":"legacy-coderetreat-episode-10-extract-class-code-cast","status":"publish","type":"post","link":"https:\/\/blog.adrianbolboaca.ro\/2015\/04\/legacy-coderetreat-episode-10-extract-class-code-cast\/","title":{"rendered":"Legacy Coderetreat: Episode 11 – Extract Class – Codecast"},"content":{"rendered":"

Extract Class – Codecast<\/h2>\n

Blog post series<\/h3>\n

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

Code Cast<\/h3>\n

This is a code cast in Java.<\/p>\n

In the previous episodes we restructured some parts of the code base. We also extracted pure functions<\/a> and applied The Rule of Three<\/a> when restructuring the code.<\/p>\n

Because we have extracted some pure functions, now we need to think if those pure functions belong to new classes. So we structure the functions in a way that they belong together from the point of view of their responsibilities. After structuring the functions we extract the class.<\/p>\n

Learn from this video how to extract a class in legacy code in such a way that you do not introduce side-effects to the existing behaviour.<\/p>\n

Read here<\/a> more about this concept in my blog post.<\/p>\n

\n
\n
\n<\/span>