The document provides tips for asking good questions when seeking help or answers online. It recommends that people attempting to solve the problem themselves first by researching, reading documentation, and understanding error messages. It also suggests clearly explaining the problem by stating what is supposed to happen, what is not working, and how the actual behavior differs from expectations. The document stresses the importance of ensuring the question is about the right underlying problem rather than just the current approach. It concludes by noting people should mark answers as accepted to help future searchers and acknowledge those providing help.
5. @danielroseman
Make an attempt to solve it yourself.
… RTFM
… search for previous questions
… read and try and understand the error
message
6. @danielroseman
Post the code!
… the bit that actually shows the problem
… but not too much
… include the error and full traceback
7. @danielroseman
Explain the problem
… say what it’s supposed to do
… describe what’s not working
… say what you see
… and how it differs from what you were
expecting
8. @danielroseman
Make sure it’s the right problem
… ask about the thing you’re actually
trying to achieve
… not the problems you’re having with
your current approach
… avoid the X-Y problem
9. @danielroseman
… it’s not (only) about the imaginary
internet points
… it helps future searchers who might
have the same problem
Mark an answer as accepted
