Refactor Lessons Learned From The Bowling Game Kata (2/2)

It’s time to close it with the big finally, a technique that allows to refactor almost any code safely.

Learning to crush the old code with the Bowling Game Kata. Prompted by the author.

Probably the best contribution of the Bowling Game Kata is showing how we can replace a big part of code, gradually, step by step, without stopping delivery. Although the example is small, the concept is applicable to a development of any size. Just look for what you want to fix, no matter how big it is, and use this guide to make a plan to rewrite it.

On the previous article…

On the previous article, I have shown five lessons to improve refactors learned from the Bowling Game Kata:

Refactor Lessons Learned From The Bowling Game Kata (1/2)

• Lesson 1: Refactor once it works. Prioritize making code functional before refactoring, as multitasking hinders the brain’s ability to simultaneously solve problems and optimize architecture.
• Lesson 2: Add new code before removing old. Introduce new code before removing old to ensure stability; this step validates the…