Agile Software Development: Refactoring

Refactoring for high-performance Agile Software Development. Refactoring for better code. Refactoring is about improving the quality of your code by simplifying your code. Simpler code enables agility, the ability to change your code quickly, to add new features, to meet people's ever changing needs.

I am using a test-driven development practice of writing tests first here. For a full understanding of what is it all about? And why is it important? Please read this article Test-Driven Development: Really, It's a Design Technique.

This repository hosts all 3 Java Magazine articles series source-code.

Here are what you are going to learn from these articles:

1. Refactoring with New Code
   1. Defining refactoring
   2. Setting up a TDD environment
   3. Renaming variables
   4. Using the inline and extract method
2. Stabilizing Legacy Code
   1. Pinning down legacy code
   2. Testing code and branch coverage
3. Refactoring legacy code
   1. Simplifying math and Booleans
   2. Adding new behaviors to refactored code

The Legacy code Kata

The legacy code kata I used it here in these articles series is inspired from Gilded Rose Kata, written by Emily Bache.

Link To Articles

1. Refactoring Java, Part 1: Driving agile development with test-driven development.
2. Refactoring Java, Part 2: Stabilizing your legacy code and technical debt.
3. Refactoring Java, Part 3: Regaining business agility by simplifying legacy code.

How it works? 🤔

Each article is divided into steps, and in each step, I have managed to have a git commit for each TDD red-green-blue change. So, when you navigate the commits, you can notice the differences, and the refactorings that has been done toward final Kata requirements.