Skip to main content.

Guide To Asking Questions About Your Code

A guide for our members to ask questions about code.

Everybody runs into problems during development that can be frustrating and seem impossible to debug. The most important thing is: if you need help, ask for help.

We provide this guide for you to ask for help effectively in Virtual Coffee. If you're still unsure how to ask for help: ask anyway. We've all been there.

  • Go through your code line by line. You want to know what your code is doing so you can answer questions. Take some notes if necessary.
  • Do some research before asking questions. You want to avoid asking questions that you can figure out by Googling your problem. You can also improve your skill in finding solutions by Googling yourself.
  • Check for some typos. Sometimes an error arises from a single typo.
  • Google the error that you encounter by copy-pasting the error message. Most of the time, you can find some answers from people who encountered the same error as yours.
  • Debug your code. You can check out Nick Taylor's Lunch and Learn sessions below about debugging:

Getting started

  • A simple "Can someone help me with {something}?" is enough to get a conversation started.
  • Be specific about what you're looking for. "Does anyone know why my MongoDB authentication failed?" is better than "My app is crashing."
  • For a more general question or when trying to grasp a concept: "Does anyone have experience with {something}?" or "Can someone explain {something} to me like I'm five?" is a good starting point.

Asking questions

  • Specified details as much as possible, such as:
    • What language, framework, or libraries version are you using when encountering the error?
    • What operating system (e.g., Windows, Mac, Linux) and version are you experiencing the problem on?
  • Provide relevant code along with your question, if possible.
  • Explain the command or steps that you run to reproduce the problem.
  • Describe what you have tried to fix the problem. It's okay if you don't know where to start, but share whatever you have already tried/ruled out.
  • Read through your question. You want to ensure that your question makes sense and you've included all information needed for other members to help you.


Ask questions about your code or ask other members' help for pairing in this channel.

You can also ask for resources, ask opinions about your project, ask for help to fill surveys, or any other support related to tech.


This channel is about everything front-end and asks questions if you have problems with your front-end-related codes.


This channel is for questions, comments, tips, and answers about a11y for accessibility.


Stuck on an algorithm? This is the place for you.


You can always drop your questions about job searching and job interviews to this channel. This group also has a weekly meeting to discuss and learn everything about tech interviews together.


This channel is to post any job postings. But, you can also drop your questions regarding job searching on this channel.


Do you have questions about Virtual Coffee? What do we do? What are we up to? Tools we use and how to utilize them? Or do you have some ideas for the community that you would share?

You can drop those Virtual Coffee’s related questions here for the community to answer.


If you are still unsure where to ask questions, you can ask them here. Some members will crosspost your question to the appropriate channel for better exposure.

Do check our complete list of channels in the Slack channel guide.

Discussion board

Do check out our discussion board on GitHub 😄! You can use it whenever you have questions or want to throw ideas around Virtual Coffee or anything else.

Back to Top

How To Utilize Slack For Asking Questions

Permalink to “How To Utilize Slack For Asking Questions”
  • Unless you are a maintainer or granted permission by a maintainer, you want to avoid using @here or @channel. Using these tags will notify everyone in the channel. It might be an afternoon at your time, but it is midnight in some parts of the world. And we want to respect our members. We are a very active community. Someone will answer you as soon as possible.

  • When you are answering questions, make sure to reply in the thread. By keeping one topic in one thread, we can prevent confusion.

  • Use a single backtick (`) to share technical jargon or a one-line code in a sentence. For example:

    Can I skip the `h2` to `h3`?
  • Use triple backtick (```) to share a code block and keep a clean format. For example:

    function greetings() {
      console.log("Hello there!");

Back to Top