undefinedfix
Sign in

How to ask questions to get better answers

Silverspur edited in Fri, 11 Nov 2022

Often ask questions in SF, but the probability of getting answers is very low.

It's the same with asking questions in the group. The big guys in the group don't pay much attention to me!

Is there any good way and skill of asking questions that can improve the probability of big guys answering my questions?

What do the big guys think when they answer questions?

Help, answer!

13 Replies
obeha
commented on Fri, 11 Nov 2022

It is suggested that we first look at the wisdom of asking questions

fearhack
commented on Fri, 11 Nov 2022

Actively maintain your own problems until they are solved. In order to answer your question, I have read the questions you have asked, without exception. In all the questions you have sent out, after the questions have been raised, I will not participate in the maintenance and communicate with the respondents.

The purpose of your question is to dispel doubts, rather than the emperor's choice of concubines. The problem is often solved through communication.

In the face of such questions, I generally choose to detour, since you asked, it might as well say.

user2647513
commented on Fri, 11 Nov 2022

1. Problem phenomenon 2. The environment in which the problem occurs, such as the version of the windows computer's firebox browser 3. The steps of reproduction, operation 1 > operation 24. My own guess

svet0slav
commented on Fri, 11 Nov 2022

Emmm ~ in an ideal state, you can pay more attention to the boss in some aspect and invite him when you ask relevant questions. If you don't reply, you'll see if he is free

aEVA12
commented on Sat, 12 Nov 2022

You can post the questions you have asked and let's analyze them again


The big guys usually don't have time to pour water. If you want to ask something in depth, the big guy may not be in this field. If you want to ask something simple, the big guy may disdain to answer

The best way to ask this question is to find the boss in the working group. The probability of them answering you should be much higher than that of asking questions on the Internet

After all, no one answers online at any time

myimprov
commented on Sat, 12 Nov 2022

Try to write the problem clearly, such as a code bug, you can cut a diagram of the code, execute SQL statements, and list the execution results, and then express the final result you want. You can edit the result in the editor, and then you know how to ask when you ask too many questions? Of course, this thing still depends on self understanding...

Az104DAYS
commented on Sat, 12 Nov 2022

First of all, don't talk nonsense. It's not as easy to ask this kind of question on stack overflow

AppStudio
commented on Sat, 12 Nov 2022

。。 You're starting again

Majiy
commented on Sat, 12 Nov 2022

Personal methods are for reference only

title

If no one else can understand the general meaning of a title, it is difficult for others to pay attention to it. At this point, you need to think in reverse. For example, when you encounter a problem and go to Google, you will definitely choose several keywords. For example, when you want nginx to support HTTPS, you usually write these keywords, nginx enable HTTPS, which can basically find the answer you want. These words contain

  • Platform (nginx)
  • Function (HTTPS)
  • Enable (HTTPS)

So I personally think these are essential, and that's why labels come from.

For example, the title of the question is changed to,

如何使用vuex实现一个简单的购物车功能
平台(vuex),功能(购物车)述求(本地化管理购物车)

content

The content should describe the context of your problem, such as you are using angular4.0. If it's an error, you need to list the errors (code or screenshot). If it's an effect you want to achieve, you need to describe the effect clearly. If it's a requirement scheme, you should provide descriptions of several schemes

paradoxix
commented on Sat, 12 Nov 2022

Original link https://discuss.laravel-admin.org/d/2--

cxxjd
commented on Sun, 13 Nov 2022

http://www.catb.org/~esr/faqs...

reto11
commented on Sun, 13 Nov 2022

Principle: SF is to help you solve the problems you encounter in your study / work, such as telling you where there is a problem with your code, and correcting the rest by yourself. Instead of writing code for you

  1. Most importantly, what's your problem? What results do you need? Refuse to reach out to the party
  2. If it is an environmental problem, how can others reproduce it?
  3. Code not screenshot, not screenshot, not screenshot, I do not want to see this
PKV
commented on Sun, 13 Nov 2022

Many friends upstairs mentioned how to ask questions the smart way. Here is a translated version of GitHub -- > the wisdom of asking questions