Asking questions is an inevitable part of software development, and the sparks of ideas often produce fantastic results, but as a programmer who is arrogant and rules the world, have you really thought about and summarized your questions? How do you ask a good question that satisfies both parties and get the most out of it? After all, life is too short to waste your time on a bad question.
Before asking questions, please ask yourself the following questions:
- Have you thought through the problem?
- You can’t do it on your own?
- Has anyone in the search engines or the community asked similar questions?
- Do I have the right questioner?
- Have you prepared your preparation materials for the question?
There is a joke: when it comes to messy technical problems, female programmers assume that male programmers can do everything; Among male programmers, the average programmer thinks that a good programmer can do everything; Skilled programmers struggle to find answers on the Internet every time…
Asking good questions is the first step in your improvement. Asking questions is the same as writing a program. There should be context, context, organization and breakpoint debugging, rather than a requirement to be asked to give an answer. Suggestions are in order: colleagues > community > software author (Github private message), be sure to balance the time, quality and response speed of the problem, after all, no one is always ready to provide you with all kinds of selfless services.
Asking questions is a knowledge, please take it seriously, in the process of asking questions to continuously improve the ability to summarize questions, analysis of questions, and constantly improve yourself is the ultimate goal, a good question will be as wonderful as a good answer, at the same time, don’t forget to say thank you to every person who helped you answer.