Skip to content

Latest commit

 

History

History
159 lines (94 loc) · 5.61 KB

how-to-ask-a-question.md

File metadata and controls

159 lines (94 loc) · 5.61 KB
Raw

How to ask a question

Note: Before reading this, you might want to read my guide on top 6 tips to solve any software engineering error.

Also note, take this pledge: "I solemnly swear that after asking a question I will spend at least 5 minutes trying to answer someone else's question. I will consult the 'How to answer a question' page before I do so. "

The internet is our documentation, and we want to treat is as such. Every specific question we have should be able to be found by typing it into a web search bar.

Now, there are no "bad" questions, but there are poorly-formatted questions. A poorly formatted question has a low chance of being answered, poor chance of being discovered, and can "clutter up" forums and discussion boards. So let's make sure we strive for well-formatted questions!

Full Examples at the bottom!

Here are the steps to ask a well-formatted question:

  1. Search to see if the question has already been asked
  2. Know where to post your question
  3. Make a title that summarizes the problem
  4. Introduce the problem before writing any code
  5. Make sure you format code using backticks (```) and a language tag
  6. Make sure you copy paste your code instead of using screenshots
  7. Make sure your code is a minimal example

1. Search to see if the question has already been asked

Do not skip this step!

We should think of the internet as one giant document. If a question has already been asked and you can find it on the first page of your search engine, it's good! Don't ask the question again!

And if it's not on the first page of your search results, then yes, you should 100% ask the question on a forum even if you know the answer.

We want every tech question ever to be:

  1. Indexed by search engines
  2. Easy to find
  3. Easy to reproduce

So that in 6 months when you forget the answer, you can just google it and it'll show up!

We don't want there to be multiple questions, because that can fragment where people look! We want to add answers, comments, etc all in one place

2. Know where to post your question

I categorize questions into one of three:

  • Specific code based questions
  • Generic theoretical questions
  • "In the know", support, or emergency questions

Specific code based questions

These are what we strive for. These are reproducible questions that help the world. You'll want to put these questions in places like:

  • The "Q&A" discussions section of this course
  • stackoverflow
  • stack exchange ETH.

These are questions that typically can have a "right" or "many right answers". Generally, these are not very opinionated questions.

These are questions like "How to convert bytes32 to uint256".

Generic Theoretical Questions

These are questions that likely do not have a canonical answer. These are questions like "which blockchain should I deploy to?" or "How could I make a game that involves many random characters?". They belong in places like:

  • The "General" discussions section of this course
  • A generic forum like Reddit, Twitter
  • Discord (like some of the ones people have started here)

Ideally, you put these on an indexed forum like reddit and the general discussions section instead of discord so others can do a web search for the problems.

"In the know", support, or emergency questions

These are very specific use cases and 99% of your questions will not be these kinds. These are questions like "we just got hacked, can you help us?", "Want to join my team", etc. They are questions that likely only apply to your situation and what you are doing. They belong in:

  • Discord DMs
  • Email
  • etc

And should be used very sparingly.

3. Make a title that summarizes the problem

It should be minimal, searchable, indexable (by search engines).

Examples:

Bad:

  • I'm stuck, please help

Good:

  • Could Not Detect Network using WSL & Ganache

Bad:

  • hardhat error

Good:

  • TypeError: Cannot read property 'length' of undefined - when deploying contract

4. Introduce the problem before writing any code

In the body of the question, say what you're trying to do, what you've done, and give a summary of your problem.

With this course in the discussions tab, you may also give a timestamp of where you're getting the issue (in fact, please give a timestamp with a link to the location in the video).

5. Make sure you format code using backticks (```) and a language tag

You'll want to format your question so it's as easy as possible to read! Especially with your code snippets.

Your code should show up like this:

// my code here

In your question, you'll type it like this:

```javascript
// my code here
```

If it doesn't get formatted, you can edit your question (usually, you can click the three little dots at the top right of your question) to make it formatted nicely.

6. Make sure you copy paste your code instead of using screenshots

We want web crawlers to index every word you write, so even copy paste errors (and format them with 3 backticks!)

7. Make sure your code is a minimal example

There are two types of code questions:

  • Debug me
  • Specific questions

Don't be a "Debug Me"

Example of a poorly formatted question (a debug me question):

Hi I'm confused my code isn't working here is all my code

// pretend I pasted like 300 lines of code here

Example of a much better question

I'm getting error x on line 42 of my code:

const some_var = "dog"
// this is the line that is erroring

More information on reproducible code.