00ASKING FOR TECH HELP

Help them
see it fail.

A person seen from behind working at a laptop on a wooden desk by a window in the evening, with a mug and a notebook beside them — AI-generated image, not a photograph of a real person or place.

A good question lets a stranger reproduce your problem.

Forum helpers are volunteers working blind: they cannot see your screen. Bug-reporting guides and studies of millions of forum questions point the same way: be specific, paste the exact error, and give steps someone else can follow.

BE PRECISEfacts first, guesses secondUpdated 16 October 2026

Check your question

01Principles

A title that names the problem
The error, copied exactly
Steps someone can repeat
Clearer questions, faster answers

02THE SHORT ANSWER

Say what happened,
not just that it broke.

"It doesn't work" gives helpers nothing to go on.
Three habits do most of the work.

THE TITLE

Name the actual problem

Stack Overflow's guide says to sum up the question in one sentence for a busy colleague. "Software crashes" is a poor summary; what crashes, and when, is a good one.

Check your question

REPRODUCE

Let them make it fail

Simon Tatham's classic guide says the aim of a bug report is to let the programmer see the program failing in front of them. Clear steps do that from a distance.

Write the steps

THE ERROR

Copy it word for word

Error messages, especially numbers in them, are vital clues. Paste the text rather than a screenshot so others can read and search it.

See the research

03A QUICK QUESTION CHECK

What are you
asking about?

Pick the kind of problem to see what the guides say to include. The bar shows how much detail helpers usually need from you.

Based on Stack Overflow's help pages, Mozilla's bug writing guidelines and Simon Tatham's How to Report Bugs Effectively.

Question check

Choose your situationHow do I use a feature?Two problems at onceAn error messageSomething crashes or breaksMy own code misbehaves

How do I use a feature?Say where you looked

Search first, then say where you already looked for the answer and why it did not help. That helps stop it being marked as a duplicate.

Two problems at onceSplit them

Mozilla asks for one bug report per issue. A 2021 study found questions covering several technical issues were more likely to go unanswered.

An error messageCopy it exactly

Write the message down carefully, numbers included. Paste it as text, not as a picture of the screen.

Something crashes or breaksSteps to reproduce

Mozilla calls steps to reproduce the most important part of a bug report. Say whether it fails every time, sometimes or only once, then give expected and actual results.

My own code misbehavesMinimal example

Share a minimal, complete and reproducible example: as little code as still shows the problem, tested so you know it really does.

Sources: Stack Overflow Help Center, Mozilla Bugzilla Bug Writing Guidelines, Simon Tatham (1999), Mondal et al. (2021).

04TWO NUMBERS WORTH KNOWING

Clear questions
get more answers.

One figure on questions left hanging,
one on what reproducible examples are worth.

≈ 29%

Stack Overflow questions with no answer (2018)

A study of 4.8 million questions found unanswered ones were harder to read, and more often about outdated technology, several issues at once, or lacking a suitable code example.

UNANSWERED · ISEC 2021

2× higher

Chance of an accepted answer

In 800 Java and Python questions, those whose problem could be reproduced had at least twice the chance of an accepted answer. Where it could not, the median wait for one doubled.

REPRODUCIBLE · MONDAL ET AL.

Researchers could reproduce about 68% of the Java and 71% of the Python problems from the code people posted; about 22% and 19% could not be reproduced at all.

05FOUR STEPS BEFORE YOU POST

Write it once,
write it well.

These come from long-standing bug-reporting guides. They take a few minutes and save a long back-and-forth in the replies.

Search, and note what you found
Look for existing answers first. If they did not help, link them and say why.
Write a one-line summary
About ten words that say what fails and when. Mozilla suggests describing the problem, not your guessed fix.
List the steps, then expected and actual
Numbered steps someone else can follow, then what you expected to see and what you saw instead.
Add versions and the exact error
Have version numbers at your fingertips and paste error text exactly. Keep facts separate from guesses.

Two people at a table leaning in towards one laptop, one pointing at the screen while the other watches — AI-generated image, not a photograph of a real person or place.

06WHEN NOTHING MAKES SENSE

Freeze,
then write it down.

Close-up of hands typing on a laptop keyboard next to a cup of tea, the screen softly out of focus — AI-generated image, not a photograph of a real person or place.

Tatham's advice when a computer does something unexpected is to stop and do nothing until you are calm. Clicking around can wipe out the very message that would have explained the fault.

If you try to diagnose the fault yourself, still report the symptoms too. And be ready for follow-up questions: helpers ask for extra details because they need them, not to be awkward.

07Questions

Questions people ask

Why do so many forum questions go unanswered?

A 2021 study of 4.8 million Stack Overflow questions found unanswered ones were harder to read and more often covered outdated technology, several issues at once, or lacked an appropriate code example.

Should I post a screenshot of the error?

Stack Overflow asks people not to post images of code, data or error messages: copy the text instead. Pictures are best kept for things text cannot show, such as a layout that renders wrongly.

What is a minimal reproducible example?

The smallest piece of code that still shows the problem, complete enough for someone else to run, and tested so you know it reproduces the issue. It may also be called an MCVE or a reprex.

What if the problem only happens sometimes?

Say so. Mozilla asks reporters to state whether they can reproduce a bug at will, occasionally or not at all, and to add as much extra information as they can when there are no reliable steps.

Should I include my own theory about the cause?

You can, but label it. Bug-reporting guides ask you to keep facts (what you did and saw) clearly separate from speculation, and never to leave the facts out.

08Sources

Help them
see it fail.