If there are tools and community-established guidelines for style and best practices, those are good for compliance because it can be automated. It also stings less when the program says your code needs to be updated, rather than seeming nitpicky from a person reviewing it.
For older languages without those, it is a slower process and takes initiative from someone that sees the problems and knows the general things to avoid. If there isn't an automated tool and you aren't looking to develop one, it requires everyone actively trying to internalize and follow the standards in any code they write, so adoption will be sporadic.
Either way, I think it needs to be incorporated into code review processes otherwise it isn't kept in front of everyone and becomes optional.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.