In many cases, I believe distaste to “abstraction-less” code is an avoidance of discomfort. “I have never programmed like this, this feels uncomfortable, therefore I label it as unclean or bad quality code”.
But then the appropriate time will not be spent designing a clean interface. Instead the abstraction is built upfront and fits the original discovered problem space but not the actual problem space.
Then the abstraction may be coupled tightly, even though it is a class or some form of layer, with the implementation. Then all bets are off.
But of course the programmer who made it goes “ah feels like home”.
But then the appropriate time will not be spent designing a clean interface. Instead the abstraction is built upfront and fits the original discovered problem space but not the actual problem space.
Then the abstraction may be coupled tightly, even though it is a class or some form of layer, with the implementation. Then all bets are off.
But of course the programmer who made it goes “ah feels like home”.