The author did not understood the idea. His description of his understanding does not include any reference to the "wrong"-ness of abstractions that shouldn't

The author did not understood the idea. His description of his understanding does not include any reference to the "wrong"-ness of abstractions that shouldn't exist. If I read him as-is, I should conclude that the idea is to never make any abstraction at all. It obviously cannot be it since that would be stupid. "Wrong" abstractions are already bastardized, from their first iteration. Developers decide to code them nonetheless because they estimate that their "awkwardness" is worth it in comparison to code duplication. What they fail to realize is that, to the contrary that code duplication which just "is there", the awkwardness of the abstraction will compound. Duplication is the last resort, when one has established that he couldn't find any non-wrong abstraction.