The “Good Enough” Refactor Rule for Fast Teams

I used to chase perfection — refactor deeply, clean every file, remove every legacy prop.

But on fast-moving teams, that’s a luxury.

Now I follow a rule I call: “Clean What You Touch.”

That means:

Only refactor the parts you already changed in a PR

Leave clear TODOs in comments, not Jira

Propose full refactors during quiet sprints, not delivery weeks

This keeps tech debt manageable without slowing features.

It also shows your team you can balance speed and craftsmanship — a signal of seniority that doesn’t need a title.