Time to Train the Nose for Code Smells

Kurly's Logistics Development Team carried out a large-scale refactoring to improve the code quality of the Inbound Management System (RMS). The goal was to improve the initially insufficient code condition and, in line with the team growing from 1 developer to 3, to raise the overall understanding of the project.

The refactoring was classified into 8 parts based on code that performed similar operations to the main functionality. It was divided into 3 stages, with QA verification conducted at each stage before deployment, and in particular, assigned parts were intentionally cross-allocated so that team members would grasp the project as a whole.

Refactoring Process and Results

• Code Improvement: Discovered and improved habitually misused areas such as null handling, Optional, and Stream usage.
• Writing Test Code: Through attempts at TDD, reduced resistance to test code and improved the ability to write it.
• Knowledge Sharing: During the process of identifying refactoring targets, shared various perspectives and discussed directions for code improvement.

The 2nd round of refactoring has now been completed and deployed, with the 3rd round planned. The team emphasizes that refactoring is not a one-time task but a process that must be continuously improved and maintained, and is recruiting talent to join logistics system development.