Conditional Polymorphism Swift Code Katas 21 Expense Report

The logic is still spread in too many places. Can we create new classes and give them ownership of these responsibilities?

With the

Before we clean up this untested

Rather than trying to force the

With the

Who passes what? We move more responsibilities, then ask how much one caller should pass to the next object. I stream at ...

First, make the change easy. Then, make the easy change. And even then, there are still some

First, let's improve the test

Last time, we got print() out of the way. Now how do we deal with Date() to make this

Need to add a feature to some gross legacy

Code Katas

How to make changes in

Break-everything-then-fix-it is not a healthy way to refactor. For these changes, I apply the Mikado Method in the small, without ...

Here I am working on the

Here I am starting to work on the

Moving responsibilities from the caller to a called object can greatly simplify your

Master the Ternary Operator in