By identifying common patterns and idioms, developers can create mental models and schemata that help them quickly understand and navigate new code.
Furthermore, by mapping these idioms to idiosyncrasies and specific use cases, developers can ensure that they are applying the correct approach and not overgeneralizing it.
One way to do this is by creating a reference or documentation that maps common idioms to specific use cases, highlighting where they may need to be adapted or modified to fit a particular project or development team.
This can help ensure that developers are working with a shared understanding of best practices and can make informed decisions about when to use established idioms and when to adapt them to fit their specific needs.
A common misconception is to use the adverbial or adjectival form of the term as "using a programming language in a typical way", which really refers to a idiosyncrasy.