Should one make a code change by beginning to refactor at the "entry-point method" or the "inner-most method" of a call-stack?
A colleague and I were talking about a code change that would go through many application layers and touch a number of classes. The end goal was to assign a variable to a SQL table name at the data provider level. But the variable would have to be configured and touched by many other layers.
We figured out that we have opposite approaches to this type of refactor. I like to start at the entry point and trickle "down," and he prefers to make the final change first and then find usages of that innermost method and continue moving "up" the callstack.
What are the considerations between the two methods? What is most optimal and efficient?