Combine error logs, version-control churn, and complexity scores to reveal files that bite you repeatedly. Rank by user impact and effort. A two-hour refactor in a high-churn module often beats a week polishing rarely touched code. Let data, not frustration, choose the next slice.
Capture one-page decisions with brief Architecture Decision Records, sequence small pull requests, and buffer risky steps behind feature flags. Aim for visible wins each week. Progress compounds when reviews stay fast, scope stays tight, and unfinished changes never block your ability to release.
Record build duration, test coverage, error rate, and p95 latency before you touch anything. After each change, compare outcomes and publish notes. Clear numbers keep confidence high, help you roll back without ego, and teach you which refactors actually moved reality, not just code.