This is the second module of series called "Pyramid of Refactoring" dedicated to achieving Clean Code.
Although Refactoring to Chain of Responsibility is not mentioned in the core refactoring books ("Refactoring" & "Refactoring to Patterns") the techniques described in these books allow to create a plan for such a refactoring journey.
The goal of the course is to disentangle the codebase from a set of deeply nested conditional if/else statements. It is a very common case - and if it is left for a long time - then it leads to a very complex legacy code after subsequent code extensions.
We use refactoring techniques and perform all the changes live. The partititants download the source code and performs all the changes together with the trainer - step by step. In this sample we make use of Chain of Responsibility Design Pattern as goal of our refactoring journey.
The journey into Chain of Responsibility allows the attendees to practice code transformations like :
Merge If Statements
Replace Temp with Query
Extract Class / Extract Delegate
Extract Interface- Rename Methods & Variables
The course ends up with Homework, where the participants can experience the difference between implementing additional requirements within Clean Code and within Legacy Code. This is the difference between skipping and applying Preparatory Refactoring.
My name is Włodek Krakowski. I am an independent technical trainer, Team Teader and also a developer - to sharpen my skills continuously.
My main interest is taking care of delivering valued software from different perspectives. These are how people take care of quality of code, how people work together towards providing business value, how people help to grow each other and how people are managed.