@GeePawHill
I wrote a little bit on that just the other day.
https://www.linkedin.com/feed/update/urn:li:activity:7055994041762508800?commentUrn=urn%3Ali%3Acomment%3A%28activity%3A7055994041762508800%2C7056048897181241345%29
Dittos!
I've never really thought this needed to be described separately, given that combining Refactoring patterns is common. [Isn't it?!?]
I look at the callers to a method and think, "This isn't quite right. There's still duplication among the callers, the parameters aren't quite right, (etc...).
So I
- Inline
- Adjust a bit
- Extract
- (And usually adjust a bit to "clean up" after.)
It's what I have to do when I realize that pulling "X" into the method was not the best idea; I should have pulled "Y" into the method instead.
@JeffGrigg @GeePawHill
That's why I called it a Refactoring Arpeggio.
Named Refactorings are Design Patterns.
And that means, to me, that they can be combined into a Pattern Language.
Not just "here's a set of related things." But "Put these 'words' together to form a 'sentence.'"
Or just that some "Refactorings" are a combination of lower level Refactoring steps, done in a certain sequence.