You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A good question is one that can be answered. Be clear about what you're asking, so that we can see what you do and don't understand.
Some suggestions:
Search for other questions on the same topic before posting.
Don't be afraid to ask a "dumb" question. If something's not clear from our documentation, our documentation needs to be improved. But make sure you've done your research first.
Ensure that the title describes the question. You may find it easiest to write this last.
Describe what you're trying to do. Include URLs to relevant pages, eg to code on GitHub, codelists on OpenCodelists, jobs on the job server, and so on.
Describe what you see, and compare this with what you expect to see.
Tell us which bits of the documentation you've looked at.
Learn about Markdown for formatting your messages. In particular, use backticks to format code.
Re-read your question before posting it, and imagine you're the person answering. Have you provided enough information? Is it easy to follow?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
A good question is one that can be answered. Be clear about what you're asking, so that we can see what you do and don't understand.
Some suggestions:
Asking a good question can sometimes help you answer it yourself. If you find this happening, ask your question anyway and provide an answer -- you may help other users, and show us what's hard to understand.
Beta Was this translation helpful? Give feedback.
All reactions