On questions with problems
A question without a problem to solve, and just casting the net for "best practices" doesn't have a problem to solve. That's rather tautologic, but that is the problem with the questions without a problem. You can't ever solve them.
The actual best practices (and not things that one mindlessly copies and pastes into documents for management, or tosses out in a meeting as an appeal to authority) are ones that become evident when solving a problem.
Thus, the answers themselves to a question that has a problem will be the best practices to solve that problem. So ask the question about the problem and you will get the best practices.
Blindly following best practices is, at best, an anti-pattern (for those who like to go with patterns and anti-patterns). As with how patterns are meant to be used, you use them when you encounter a problem - you don't just take half a dozen patterns and toss them together to get an application. Likewise, with best practices you should use them when you need to.
Asking for "what are the best practices for writing an Android application" is very much the same question as "what are the patterns you use for writing an Android application" - both are too broad and not useful to other users (there are dozens of patterns and best practices - and dozens of possible answers).
On problems with answers
The other half of the problem with asking for best practices is the quality of the answers. This isn't so much a problem with the question other than it encourages such answers.
When someone asks for best practices, everyone chimes in. This is often exacerbated by having the question show up in the hot questions which magnifies the problem with answers.
What is the best practice for XYZ?
Which leads us to get answers like:
At my shop, we avoid doing X.
At my shop, we avoid doing Y.
At my shop, we find that X and Y are both essential to the proper workings.
Z is always problematic when you are working with ABC.
The very nature of those answers is forum like and brings with it the problems of forums. You get lots of answers that don't have a single answer. It is too broad and laden with opinions.
Now, I admit the straw man above and its quite possible that the answers will be better than the ones above. But they won't be as good as actually presenting the problem to be solved and having those answers.
A takeaway of Optimizing For Pearls, Not Sand is that while poor questions can produce great answers we really need to try to have questions that lead to great answers from the start.
That’s why we’re determined to keep question quality high, even at the cost of refusing a little sand. It’s true that you can’t have Q&A without questions, but having the wrong sorts of questions is far more dangerous. The fastest way to kill any Q&A site is to flood it with low-quality questions.
When you get dozens of poor quality answers in a question (such that asking for best practices can easily produce) the quality of the site suffers. The signal to noise ratio goes down. And whats worse, the way to fix this is easy - don't ask about best practices in the abstract - ask about the problem you are encountering.