Refactoring Kata, allowing to manipulate multiple concepts and techniques:
- Tell don't ask principle
- Anti pattern anemic domain model
- Eventually use the Mikado Method or a phase of Exploratory Refactoring
- Eventually apply the Tell! Don't ask! constraint
- Eventually apply the Object Calisthenics rules
- Apply Parse, don't validate principle (Type-driven design)
A kanban, to follow all the refactoring steps you identify, is higly recommended
Original: Gabriele Tondi's version
You have to take the responsability of an application where the former developers first experimented the clean architecture.
This application being responsible of many bugs, you are tasked with refactoring it to make it more maintainable and reliable