Some complexifiers are not nearly as smart as they seem - they can often have tunnel vision due to their brilliance in specific domains, and miss the big picture. Which puts them in the "dumb and gets things done" quadrant: https://www.johndcook.com/blog/2010/12/27/dumb-and-gets-thin...
I tended towards this but was - I guess - lucky to have had a manager who identified this and helped me grow.
My approach: the young ones need to fail. Hard. Then they'll learn.
The older ones who failed and reacted badly (it was everyone else's fault). I take them out of their comfort zone, tell them about my experiences and talk about the feeling of self-doubt when moving to different domains. Work with them to turn them into truly excellent team members (which they - in my experience - can be as they're usually driven, hard working and egotistical).
Turns out the blog linked in the first post was written by the same person.
- smart person, identifies a problem, wants to solve it with more complexity.
- normal person, doesn’t notice a problem (or doesn’t care), doesn’t attempt to address it, creates more incidental complexity.
The former is a complexifier. The latter is a typical dev.
Typical dev wants to do whatever is easiest. Complexifier goes out of their way to “fix” things.
Aka big brain developers