Partner Office Renewal: Why We Refactored

Oliveyoung's Partner Squad carried out a large-scale refactoring to improve maintenance efficiency for the platform serving partner companies. The existing code suffered from readability and scalability issues caused by unclear use of abbreviations, inconsistent naming conventions, and excessively bloated general-purpose classes (such as EtEntrBaseEx).

The refactoring proceeded in the following 5 steps:

• Define code style conventions: Establish a consistent style guide within the team
• Separate general-purpose classes: Redefine a massive class with 158 fields into domain-specific VOs
• Remove unused code: Delete unused variables and methods
• Ensure type safety: Change String-based status codes to Enum
• Improve business logic: Simplify logic by separating responsibilities concentrated in a single method

As a result, the number of code lines for a specific service logic was reduced by 60%, and the overall number of code lines in the package was also reduced by approximately 30%.