Shulou(Shulou.com)06/01 Report--

This article introduces how to ask an elegant question in big data. The content is very detailed. Interested friends can use it for reference. I hope it will be helpful to you.

It's a clich é about asking questions. Occasionally you can see posts calling for correct questions, but it seems that many people do not attach great importance to the way and value of asking questions.

When we throw a question to the outside world in life, whether it can be answered or not depends to a large extent on the way we ask it. After hearing the Tao, specializing in the art industry and asking others for advice is something that everyone cannot avoid. In the three-person walk, this is what my teacher must say, so generally speaking, we all encourage people to ask questions, ask and answer questions, which is in itself a process of mutual learning and enlightenment between the questioner and the questioner. But in reality, the interactive process between questions and answers will give rise to questions due to the improper questions of the questioners, and the level of questions will directly affect the quality of the answers.

Therefore, the above-mentioned encouragement to ask questions is not a complete understanding of the questions. Confucius said that there must be my teacher and should not be ashamed to ask questions. Today, we have to add the meaning of asking questions correctly. Technical people encourage questions, but it is not that we encourage casual questions, but that we encourage insightful questions on the basis of making full efforts to get answers by ourselves.

What should be done before asking questions in general, everyone has their own business and is busy about it. Taking up a lot of other people's time by asking questions is a sad thing in itself. for most people engaged in professional skills, time is more precious than anything else. So before asking questions, it's best to make sure that your questions don't become time killers for others. But nothing is absolute, maybe your question can't get the respondent to say a word or two, or the person who is willing to answer your question is patient or old-fashioned. Even so, we need to make sure that the following two principles are met before asking questions.

The first is not to ask stupid questions. The second is not a lazy guy. These two principles usually complement each other. Some friends ask stupid questions because they don't want to search for answers themselves, while others casually ask questions that no one wants to answer because they don't want to think. So, the first question, what is a stupid question? Stupid questions are questions that the questioner can get answers from search engines by using his or her head and hands. Everyone should show contempt for this kind of question, such a person only wants to be a hand-holding party and wants to get it directly from others, so as to waste other people's precious time for selfishness. We classify such lazy people as the most annoying kind of people. Typical stupid questions and lazy guys

After grasping the two basic principles, we can generally avoid the questioning situation of most people. In this process, you need to make good use of search engines so that you can efficiently find answers to questions from the Internet. Proficiency in Google search and finding answers to questions on Stack Overflow, GitHub Issue, Quora, Medium and Reddit are basic skills that every technical learner should have. Why do we attach so much importance to solving personal problems through Internet search? First, there are a lot of open source materials on the Internet, which are enough to solve some of the problems you encounter. In addition, 99% of the people who have encountered problems and trampled in the process of learning as a beginner have encountered problems and left solutions on the Internet, so all you have to do is to throw your Error Information into Google.

For example, the following figure shows a simple error report from Python. The list index exceeds: IndexError.

Even if Xiaobai beginners encounter this kind of problem, they can solve the problem by themselves according to the error information of the code, and copying the error report to Google with a little bit of trouble can also solve the problem quickly. If someone still wants to ask this kind of question, not to mention whether the person being asked will answer you, he may question your learning ability very much.

In addition to using search engines, many tools, programming languages and code usage problems will be given to the corresponding Manual or Tutorial. For example, you will use R help to learn R language, and learning PyTorch officially gives you a very complete PyTorch Tutorial. PyTorch Tutorial

So, some self-exploration work before a formal question is likely to solve 80% of your personal problems, and in the process you are proficient in how to use search engines and learn how to distinguish the flow of information obtained. know where to find the answer to a question, and over time, you will be a person of great learning ability. At the same time, it also saves other people's time, which greatly reduces the probability of becoming someone else's time killer. It can be said that your success is determined by your search and reading before asking questions.

Nine times out of ten, life is not what you want when asking a formal question. Search engines can solve 80% of the problems we encounter, but we always have to face the remaining 20% that we can't solve on our own. So at this time, be bold to ask others questions. After preparing for the question, it is believed that 99.9% of the people will no longer ask stupid questions, and the questions asked must have been made with effort and careful consideration.

At this point, we should also pay attention to some problems to make our questions easier to understand and get feedback quickly. First of all, the platform or way of asking questions, if you are colleagues and classmates around you, sort out the logic, organize the language, and find the other person directly to ask questions. There is generally nothing wrong with offline questions and communication. But there are not many people around you who can ask for advice at any time, and many people are still used to asking online questions. For example, ask questions through Wechat, email the author about the code of an open source project, and so on.

One of the most important aspects of online questions is language description. Just like asking others face-to-face, you should first sort out the basic logic, what you want to do, what methods you try, what tools you use in what environment, what problems you encounter, which shows that the answers found through search engines can not be completely solved, and so on. In general, you need to express the context of your problem in simple words. Do not underestimate this point, many times the questioner's language ability can be described as confusion.

Bad case

Let's take a look at the bad case above. As a consulting question, the questioner first makes a sentence-by-sentence introduction to his own situation, letting the questioner know which school he is from and that he is a senior. Then the student asks his question directly, wants to find an algorithm job, and then asks what needs to be done. I don't know how you will feel when you see such a question. As far as the author is concerned, my first feeling is that I don't want to answer a word. Even if I have the will to answer, I don't know where to start. First, the student must not have done any research before asking the question, even if he typed the question intact into Google, otherwise he would not have asked such a question. Second, even if they do not do research, tell their own situation in more detail, have professional background, what kind of training, which direction of the algorithm do you want to do, and what are the relevant competitions and school projects for the algorithm post itself, and so on.

Let's make some changes to the bad case above, and you can make a comparison: bad case correction

After the revision, although the question is not very good, but at least it has something to say, introduces more self-situation, and the questions asked are relatively specific, so that the person asked has a point to answer.

The second is to be careful not to step on mines when asking questions. Generally speaking, it is very likely that an interactive question-and-answer process is not enough to help you answer your questions. At this time, it is very important to ask questions, such as the following example: bad case

The questioning of the questioner can be said to be very bad. As for the answer of the questioner, the questioner should have a basic understanding of the unknown concepts of the other person's answer, just like the process of solving the problem by himself before the question, and try to understand the other person's answer. The way of questioning in the picture is a typical one without thinking.

It is also important to pay attention to politeness. As the saying goes, it is not strange to be polite, and no one will blame you for being polite. It's not about being polite, it's just basic conversational politeness. Say hello at the beginning of the question, and others will say thank you after the answer. That's all. I believe that the following kind of conversation is only a minority, and most people can't do it. Bad case

Finally, I would like to talk about questions related to the code. After all, code-related problems account for most of the time of technical learners. Where there is code, there will be bug, and if bug cannot solve it on its own, it will ask for help from the outside world. When asking people about the code bug, it is best to state under what operating environment the bug was generated. For example, in the Linux Python3.6 environment, the code reported a RuntimeError at line 8, and Google tried to solve all the problems, so it will be very specific when describing it to each other. Code queries between experts may present problems by making bug test cases, which is not a common requirement, but it is usually sufficient to be able to describe your running environment, Bug location, and expected results. When you look up problems on Stack Overflow, you can pay attention to how others describe their own code bug.

The ultimate goal: to exercise our ability to solve problems quickly, asking questions is always a means and method to solve problems. For technical learning, our ultimate goal is to improve our ability to solve problems quickly. Everyone should take this as a goal. The use of search engines to quickly solve bug, good communication and questioning habits and strong self-learning ability are the embodiment of a person's personal ability. This is the end of the elegant questions about big data. I hope the above content can be helpful to you and learn more knowledge. If you think the article is good, you can share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.