refactor

To refactor large functions and duplicated code safely, follow a structured workflow: understand the code, plan changes, execute incrementally with one refactor per commit, and verify behavior by running existing tests after each step.

Reducing technical debt in a legacy module involves applying patterns like extracting smaller functions, renaming unclear identifiers, and reorganizing code structure incrementally, ensuring existing tests pass after each change to prevent regressions.

Yes, you can restructure code to improve maintainability without changing external behavior by applying refactoring patterns like extract, simplify, and rename, while continuously verifying that the existing test suite passes after each incremental modification.

Yes, refactoring requires existing tests to be running before starting. You must run the test suite after each incremental change to ensure the code's external behavior remains unchanged and no regressions are introduced during the cleanup process.

You should not use an incremental refactoring approach when the codebase lacks existing tests to verify behavior, as the process relies entirely on running tests after each single-refactor commit to guarantee no functional regressions occur.