Have you met, for instance, the "clean architecture" paradigm? No there are definitely patterns that will be used by developers which end up getting in the way of the intent of the code, making it harder to reason about and maintain over time.

The example that I had to deal with most recently used a "clean architecture" approach in an api. The incoming calls went through three layers of redundant code - of which each layer had its own set of unit tests - before hitting the db and then passing up the response back through the stack.

It deeply annoys me to have to deal with people who have some pattern like this that they read about and, I assume mostly due to its relative obscurity, they feel ... smart? ... when applying it and forcing whomever comes after to deal with it.

To say that I want to viciously rip out the redundant layers is an understatement.