The following writing will highlight a question following the guidelines by Eric Raymond. I will provide a good example of how to ask a question or the “smart way” and a bad example showing the “not smart way”
A synopsis of this issue is relating to an issue in the user’s code. The title of the issue is very specific to the issue and includes the platform the user is using. The question is very detailed and shows multiple snippets of code that were snipped from a larger file. The user explains what exactly they are trying to do while showing the code that is most relevant. User then explains that his approach and why it might not be the best but this shows his competence, research and understanding of the context. User layers the question by explaining their purpose, the problem and finally, the question. User then finishes with courteous regards for anyone reading and willing to help. I found this a very “smart” way to ask a question.
https://stackoverflow.com/questions/65946538/c-pointer-array-fill-single-item-but-all-items-filling
A synopsis of this “not so smart” issue relates to a problem with a user’s code that seems to be a homework question. The title of this issue is very vague and seems a google search would have found a solution for their problem. To me, this shows that the user didn’t take the time to research to fix their code themselves. The user pastes their entire code then a snippet of the area they are having troubles with and finally a screenshot of the code being ran. I find most of that to be unnecessary and the only code that should be posted is of the actual issue specially written for asking the question to avoid convoluting the question. If the user took the time to break down the code for asking the question, I believe they would have solved the issue themselves. I would recommend to this user to take a few hour break then come back to the problem as our Professor recommends.