Too much abstraction can always be refactored down to less abstraction. (Too much abstraction means that there's abstraction that is unnecessary, thus it can be cut away.)
Too little abstraction means your code is too closely coupled. When the code is fresh and small, then ofcourse it's not hard to abstract out a method to DRY something up. But when your code is big and old this will quickly approach infeasability, which is the reason many projects fail.
I would go as far as saying that the science of software engineering exists because your statement is false :P
That directly contradicts my experience where most refactoring introduces abstractions when they are needed.
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.
Of course there is a golden path in the middle, but it is closer to my side ;)
This is done via simple dependency injection, which is pretty standard in many other languages outside of ruby.
Too much abstraction is way way worse than too little, as well.