3 ms·
So you're saying that the arrow of refactoring generally points in the direction of less abstraction? That directly contradicts my experience where most refact
by andybak 14y ago
So you're saying that the arrow of refactoring generally points in the direction of less abstraction?
That directly contradicts my experience where most refactoring introduces abstractions when they are needed.
- ncallaway 14y agoMy interpretation was that he was saying the arrow of refactoring is <i>easier</i> when refactoring in the direction of less abstraction. I suspect he agrees that generally the arrow points in the direction of <i>more</i> abstraction. This would be the problem he thinks exists. Not sure where I stand on either side of this; just trying to clear up what I saw as a miscommunication.
- tinco 14y agoYes. Usually when programming one encounters problems that are solved elegantly by introducing abstraction. The parent argues that doing this too eagerly results in a big mess that should be avoided by being cautious with abstraction. I argue the converse, being too cautious with abstraction can result in a big mess and you should be eager to abstract. Of course there is a golden path in the middle, but it is closer to my side ;)