Doing technology is like learning: first you have to have a good attitude, second you have to be diligent in thinking, you have to be able to endure hardship, and finally you have to learn well.
- attitude : Rigorous, simple, practical, tenacious, not impetuous
- thinking : Multi-angle, multi-dimension
- hardship : willing to deal with a problem and poor very can
Case
Here is a very good example of initiating a question, and let's take a look at how the question is raised here:
First, affirm others ' projects, and give thanks and respect to the people who created the project. And explained that I chose this project because this project is very awesome.
Next, tell the project's founder that he is having problems using the open source project. and explain that they do not encounter problems immediately to ask questions, but after a lot of ways, tried a lot of solutions, did not get resolved, and then put forward this issue. For example, the article mentions "I follow the steps of your document, and I tried a lot of solutions through Google search, but still did not find a way to solve the problem, please give me a little wisdom".
After explaining this, the point of view is expressed and the story is clarified. Here is issue itself: "According to the requirements of the installation and configuration of Vagrant and VB, through the Gitbash set up the relevant configuration, everything is normal." However, no matter how hard I try, I can't connect to the server via SSH. The command line then returns an error and says the error message: Blablabla ... "
Carefully describe the process of the operation, as well as the timing of the error and the error message returned. This information is very helpful in solving the problem quickly, and it is the key point to determine the problem at a preliminary or direct conclusion.
Once described in the paragraph above, the timing of the error and the entire operating process are clearly stated. This is followed by a description of the details of each operation in the operation process:
As mentioned here, the operating system environment is WIN8X64,SSH Keys was created by Gitbash and saved in the. ssh directory, trying different command-line terminals but none of them work correctly. But SSH can be associated with other servers (stating that your SSH should be no problem). A variety of virtual machine-related attempts, such as system restart, delete, and rebuild configuration, have been made, but the problem remains. Also through the VB interface to check the port settings, and try to modify the port configuration, but it is useless, but also through the Netstat-a check the port situation. Then a series of operations were attempted by vagrant related commands, and the server could not be connected by a gradual attempt on the document. Also tried to read Google out of the various solutions, but did not solve the problem.
Finally, please give me some help, I really want to use your setup file!
The art of doing things and scholarship.
- Select a project to select a project that meets your needs in many open source projects.
- Make sure your choice is scientific, and once selected, spend the best effort to apply it to your project.
- Encounter problems, the first thing to do is to carefully check their own operations against the official website is not a problem, rather than directly to ask others to answer.
- After checking the use method fully meet the requirements of the document, the problem remains, the idea of solving the problem continues to spread around (not limited to relying on documents to solve problems, such as the steady mention of the check port and so on), still did not go directly to find the answer.
- Exhausted the entire knowledge structure of the individual, still can not solve the problem, with the stupid method (excluding the law, such as whether to try their own SSH can connect to other servers, etc.) began to check the relevant environment, whether there is a problem, still did not directly ask people to answer.
- The exclusion method also can't locate the problem, start Google Help, filter and identify which search results are likely to solve their problems, or not directly to the answer.
- Attempts to filter out possible solutions are still not directly open to issue seeking answers.
- It still doesn't solve the problem through Google, and it's already poor. At this point, can only ask people to answer.
- Ask the answer is also a doorway, first of all, figure out who you should find the answer. Must be to the most authoritative place to find the answer, rather than casually looking for personal discussion (can be less detours, but also to avoid fraught). The open source project that you use, the project development team is of course the authority, so he submits issue to GitHub.
- The last is the art of questioning, such as wording, how to ask questions, how to throw details, and so on.
The art of questioning
First, based on their own solution, determined through a self-force can not solve the problem, then seek help from outside. There must be a process of thinking for yourself, which may not be the most efficient, but it is definitely a great help in improving your ability to deal with problems. When asking for help, be aware of the following points:
- Background note: Describe as much as you can about what you have done
- The problem itself: Describe the problem itself in as much detail as possible
- Environmental information: Provide as much detail as possible to help others to determine the key points of the problem
At last
This address: http://www.cnblogs.com/kelsen/p/6259647.html
About this article if you have any suggestions or questions, please contact the following message, but also through the Web front-end senior Engineer Group to communicate online.
Developer's Art of problem solving: How to gracefully ask questions you don't understand