Developers: Do you know the right way to ask for help?

Developers: Do you know the right way to ask for help?

·

3 min read

We all run into walls and get errors in our code that we weren't expecting. Sometimes, there's a problem we're trying to solve but are unsure how to go about it.

Before you go searching online, really give it some time and thought.

I know that 80% of influencers online tell you to "just Google it". I disagree.

That's a horrible first step.

The absolute first step you should take when you run into problems with your project should not be to find how other people can solve it for you.

Your first step should be to study your code again, study the problem you're trying to solve, and brainstorm solutions.

This brainstorming doesn't even need to be in code. Use pseudocode. Write down your problem in standard English and then explain what you think the solution can be.

A good portion of the time, the answer is right there, we're just confused because we are too caught up with the syntax.

Always remember, developers are problem solvers.

What to do next?

One you feel like you've tried your best to solve your own problem and still can't seem to resolve it, sure, reach out for help. Be it Stack Overflow, Twitter, YouTube Channels or Discord, just make sure that you do it the right way.

Copy this template. I guarantee that you will get better answers and if you ask your questions following this template.

1. The Problem

Explain what your problem is first and be as clear as possible. Focus only on the problem here.

2. Steps to Replicate

If you're getting an error while trying to install a new update, or push changes to Git, or your code was fine yesterday and today it's broken, jot down the steps required to replicate the problem.

The person who is trying to help you will need to be able to replicate the same exact problem so that they can give you a useful answer. It's no use asking for help, getting some random answer and then making that person feel useless because they have had to guess what the real problem is.

3. What I Have Tried So Far

In this section, you really want to explain what you've tried to solve the problem.

This does two things:

  1. It shows that you've been proactive with trying to solve your own issue, and
  2. It gives other people an even better idea of the problem and try to provide you with solutions you haven't tried yet.

4. Screenshots / Code

Show something of your problem.

If you are sharing code, make sure you copy and paste it in a code block or share through CodePen.

// Don't make people have to type up your code.
// Give them somewhere to start with.

Only share screenshots of errors or notifications. Even then, I wouldn't really recommend screenshots because it makes it difficult for search engines to scan the error and suggest your question to others with the same inquiry.

5. Thank Them in Advance

Please be polite. Most of the time, you're getting answers for free. Be kind. Be grateful.

TL:DR

When you run into errors and problems with your project, don't immediately resort to Googling answers. Try to solve it yourself and if you still can't resolve your problem, ask for help.

When asking for help, making sure that you split your question into 5 sections:

  1. The Problem
  2. Steps to Replicate
  3. What I Have Tried so Far
  4. Screenshots / Code
  5. Thank Them in Advance

I hope this helps. Happy coding