That might not be representative of the Perl community as a whole really ... Perl is used in corporate environments where "code golf" or "super clever" solutions will get you odd looks, Perl isn't an excuse for writing unmaintainable code, even if it's straight from PerlMonks. Books like "Modern Perl" by chromatic and software like Perl::Critic have moved the focus from writing "clever" to writing maintainable code in the last couple of years. In my opinion, it was too little and too late though and lacking supporting changes in Perl's implementation to reverse the trend (i.e. losing users).

For people who have touched saner languages (like Go) in the mean time, it's just hopeless to keep messing about with Perl, no matter how disciplined people are and how supporting the toolchain is (I run Perl::Critic and perl -MO=Lint -c before every commit and it takes longer than "go build", which checks code much more thoroughly).

The voting system of PerlMonks rewards this.

Trying to force that culture of expression and code gymnastics to write a maintainable codebase just isn't worth it in my opinion.

Don't adopt a voting system like that of PerlMonks in your business, I guess. Or else hire responsible adults. That seems straightforward enough.