CodeNewbie Community

Cover image for Guide To Asking Questions About Code
Ayu Adiati
Ayu Adiati

Posted on • Updated on • Originally published at adiati.com

Guide To Asking Questions About Code

Hi Friends 👋

In my early stage of learning, I had no one to ask questions.
I had to Google and rely on Stack Overflow to find answers.
As a newbie, I didn't know how to start asking questions and how I should ask my questions.
At that time, looking at how mean people react to newbies or accidentally repeated questions on Stack Overflow was one of my reasons not to ask questions.
I was sure my questions would be foolish because they would be a super beginner. And what if someone asked these questions before but in a different format that I'm not aware of?
My survival thought was, "I better get frustrated than bullied." 😅

But then I find out that there are no stupid questions regardless you're a newbie or not.
So, if you need help, ask for help.

Background

Our members at Virtual Coffee gathered ideas on how to ask questions.
And I recently helped put them together into a Guide To Asking Questions About Your Code and got it up on our website.

It's very critical for developers to know how to ask good questions.
So, without further ado, here is a guide to asking coding questions.

How To Ask Questions

Before Asking Question

  • 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 experienced the same error as yours.

When Asking Questions

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 others to help you.

Final Words

Last but not least, remember to thank people and be kind. They spend their valuable time reading and helping you answer your questions.


This guide was originally created as one of the member resources for Virtual Coffee.

Thank You Notes

Special thanks to David Alpert, Jonathan Yeong, Dan Ott, Abbey Perini, Mark Noonan, Travis Martin, and Claire Martinez for throwing ideas and making this guide possible! 💙

Additional Resources


Thank you for reading!
Last but not least, you can find me on Twitter. Let's connect! 😊

Discussion (0)