It is an abstraction, it's DRY. /s When I see these kinds of 'refactorings', I ask the author, what are the factors? If they can't immediately answer they didn

It is an abstraction, it's DRY. /s When I see these kinds of 'refactorings', I ask the author, what are the factors? If they can't immediately answer they didn't have them in mind and were mindlessly refactoring. Common with devs who learn the rules but not the whys. Refactoring is sometimes what gives tech debt a bad name, you trade one for another without the promised gains. Just because certain divisions were made with seams separating them, what indicates they were the right ones? I prefer to call it factoring (possibly with different factors) with stated factors.