I think there's a lot of utility in trying to achieve some conceptual consistency across a large codebase worked on by many people. Most organizations of even 12+ developers wind up with an internal informal "pattern language" that you learn while onboarding, and it can be wildly helpful if that's explicitly acknowledged as an area of knowledge to help new teammates acquire.

To me a lot of the tension comes from the "endless september" nature of software, that over the last 20 years we just keep absorbing more and more new-ish folks who come in with vastly varying levels of formal and informal education.

I'm tempted to describe one mindset as "catalogers" in contrast to other mindsets that might be called "explorers", "consensus builders", "hackers", "do-ers", etc. (not a complete list nor entirely disjoint categories -- i'm a lousy cataloger!)

I think part of this endless Design Patterns discussion is that some, myself included, would like to push back when "design patterns" starts to become "a standard and nearly exhaustive catalog that the whole field uses with uniform meanings."