This is normal issues with developers i think. Even if most developers don't recognize it.
For example, the GoF design patterns to me could be a factor for brain damage issues. (You're swimming in tons of patterns, but you've lost in connection of those patterns, how to apply it in real world problems)
Or the DDD book (Blue book) could be a brain damage book. (I found the author is a genius on writing non-sense things, mostly abstract but useless in real world for hundred of pages !, he should write about Functional programming concepts instead)
How to cure ? Stick to FP, never do OOP again.
Also avoid over-engineering in most case. Keep things simple.
For example, the GoF design patterns to me could be a factor for brain damage issues. (You're swimming in tons of patterns, but you've lost in connection of those patterns, how to apply it in real world problems)
Or the DDD book (Blue book) could be a brain damage book. (I found the author is a genius on writing non-sense things, mostly abstract but useless in real world for hundred of pages !, he should write about Functional programming concepts instead)
How to cure ? Stick to FP, never do OOP again.
Also avoid over-engineering in most case. Keep things simple.
TLDR: Avoid the wrong abstraction.