WMS Development Team Resolves Technical Debt Through Pair Programming and Systematization

The Outbound Service Development Team (WMS) had accumulated technical debt—including duplicate development, inconsistent code style, and insufficient domain understanding—due to the lack of systematic processes typical of startups. With the arrival of new team members as a catalyst, the team introduced pair programming to raise domain knowledge across the board and reorganize its development system.

Pair Programming and Domain Knowledge Sharing

The 6 team members formed pairs of 2 to 3 people, each including someone with 'medium' or higher domain understanding, and conducted real-time collaborative development using IntelliJ Code With Me. This enabled knowledge sharing, fast decision-making, and real-time code review, and process diagrams were used to grasp API-level flows.

Establishing Development Standards and Branch Strategy

Since immediately making the entire system into clean code was not possible, the team selected encapsulation, strengthened validation, and removal of duplicate code as common improvement points. The team adopted Google style for code style to improve readability, and clearly divided the Git branch strategy into master, stage, qa, and feature to secure development ownership.

Collaboration Process and Decision-Making System

Code reviews require approval from at least 2 people, and for urgent decisions, a Buster Call was convened to assess impact. For minor agreements, Slack polls were used, establishing a flexible collaboration culture suited to a remote work environment.