Asking Good (Technical) Questions
on Stack Overflow
Presented by Oded Coster
@OdedCoster
Developing as a Developer
Stack Overflow meetup
June 16th 2015
Who am I?
- Early user of Stack Overflow (August 2008)
- Developer on the Stack Exchange Q&A team
Overview
- Why should we ask good questions?
- How do we ask such questions?
- Stack Overflow specific advice
Why ask good questions?
Someone might have the answer
Why ask good questions?
It can clarify the problem to yourself
AKA Rubber duck debugging
Research your problem
- Official documentation
- Tests and experiments
- Google
- Stack Overflow search
Take your time
- Read and re-read your question
- Short, descriptive title
- Pertinent tags
- Ensure the whole makes sense
- Once posted, stay around and respond to comments
Make the question easy to answer
Make the question easy to answer
Show your research, explain what you tried
Make the question easy to answer
Make the question easy to answer
Include code that shows the problem
Make the question easy to answer
- Ask about the problem, not your attempted solution
- Limited scope - should be answerable in a few paragraphs
- Should have an objectively correct answer
Keep those who answer in mind
- Volunteers that are giving their time and expertise
- Strangers on the Internet
- From around the world
- Mostly at their place of work
Details that matter
- Don't forget to actually ask a question
- and just one question
- Check your grammar and spelling
- Be polite, but no salutations
- Don't include unnecessary details
- Formatting - learn Markdown
Downvotes, On Hold & Closing
- Don't take them personally
- Directed at the question, not you
- Hint that the question needs improving
- Closed questions can be reopened
- Deleted questions can be undeleted
Recap
- Asking good questions matters
- Take your time to ask
- Make it easy to answer
- Be mindful who you are asking help from
- Don't take feedback personally
Questions?
I'm will around - feel free to ask me anything :)