Refactoring

I haven't written about refactoring in a while. My team and I have been reading 'Refactoring by Martin Fowler' and recently worked through the TaskList kata as a refactoring exercise. This experience inspired me to write this article, which focuses on cultivating a 'refactoring mindset' – a deliberate and proactive approach to consistently improve your code.

What would it really mean to write code without automated tests, to deliver software without automated tests. Why would someone even think of writing code today and adding tests later?

This article is in continuation with the previous article "Let’s define Legacy code" where we defined Legacy code. Let's understand "Broken Window Theory" and add a new feature to Legacy code.