What we tend to mean is, "Tell me where the bodies are buried" or "What are the accepted ways to solve this problem" or "I want to know about the common errors so I can avoid them." The problem is... when you write an article that answers those questions, it has lousy SEO or at least is long-winded.
As a result, we authors and editors slap on a title of "FooBar Best Practices" anyway.
Unless there's another phrase you use, instead? If you want to read an article that summarizes "Things that serious techies learned the hard way," what would you type into a search engine?
Really handy, but it takes a good 10-20 minutes of browsing to get an idea. There are a lot of false positives and forks.
On the other hand, there is nothing better at actually seeing code written in a real project and judging for yourself how readable it is.