This is the first article in the IT career series (preface, column directory), and the second article of loosely coupled programming (column directory ).
Learning from experts is the wish of every newbie, but the biggest problem encountered is that no experts are willing to teach. This article mainly aims to solve this problem.
Learn from the following experts:
Being good at observation doesn't require a good expert to speak, but also learns from the master, that is, relying on more observation. 1. Observe that not all masters of the Code are willing or have time to guide the novice. Therefore, if you can get the code of the master, you should learn more. First, start with a relatively studious part, such as the naming method, code indent, followed by the function, class encapsulation method, and then the entire program architecture method. Many people complain that they do not have the guidance of a master, but they have passed through a lot of good code without learning it. One way is to imitate the style of expert programming and ask where you don't understand it. Experts are generally happy to answer why they are doing this, because they have accumulated many years of experience and are proud to share them. But don't ask low-level or vague questions, for example, "how do you think the naming rules are good ?" Many people who have been programming for a long time cannot say it, even though they are doing well. These are all things that need to be learned in imitation, rather than word of mouth. 2. There are many things that can be observed by observing the work habits and work environment of experts, not limited to the Code itself. The method used by the experts to type, use the shortcut key, open the window, use the input method, select a text, copy and paste the method, and switch the window ...... Any difference between a master and a novice is worth learning. For example, the fastest way to see the effect after modifying the HTML code is: Alt + F + S + tab (save and switch to the browser), ALT + d (locate to the address bar ), enter (Press enter to refresh). It looks like a long combination of buttons, but it can be around 1 ~ Completed in about 2 seconds. Although these techniques seem to be unable to take up much time, they may take up to half an hour in a day. With the improvement of your own operation experience, you can focus on programming, and the actual time you can get is more than that.
Be good at asking questions. 1. think more and ask less. Many new users hope to know the answer and bypass the complicated process of seeking knowledge. In fact, this is really bad. Two years ago, I learned both HTML + JS + jquery + Asp.net + C # + LINQ + MVC ...... These new things have long and inefficient searching for answers on the Internet. However, after a while, I suddenly felt that, the answers to many new questions seem to have been seen as early as they have solved the old ones, and can be found as soon as they are searched. In the future, we will find that most new questions have even known the answers for a long time. So,
The process of solving the problem should be regarded as the accumulation process, rather than the process of finding the answer to a single question.It will be of great help in the future. 2. Q & A experts generally seek to solve low-level problems and do not want to solve problems from the ground up (because problems are often "problem sets", some are key issues, and some are low-level problems ), instead, I like solving key problems. So every time I ask a master, I finally solve half of the problem and find the best expert with some half-cut answers. Experts will also feel respected,
Because experts feel they are being asked questions, rather than working for new users.3. "active" questions have previously mentioned active search, that is, do not expect to be able to search for answers directly, but analyze and think about the search results each time, or change the search keywords, maybe you can change the search website and find the answer on your own. This is what you mean by asking questions. When you are suddenly asked questions, the experts do not know much about the causes and consequences. On the contrary, new users who ask questions may better understand these problems. At this time, you cannot expect the experts to give answers directly. Instead, you need to analyze and think about the answers, and even ask questions by yourself.
This way of thinking is also called
Sherlock Holmes thinkingMethod. Sherlock Holmes was not the first to arrive at the scene, nor did he know the most, but he was always able to infer new clues from what others saw. It is because he can think more and take the initiative to ask questions.
Being good at InterAction, no experts are naturally obligated to help new users because they also have their own jobs. In addition, from the perspective of the company, experts are more competent to work. If they are entangled in helping new users solve problems, productivity will decline. Therefore, pay attention to the methods and methods. 1. Do not ask questions because you need them. If you feel that the experts are working to solve your own problems, wait. If he gets up and drinks tea or chats with others to discuss the problem, he can mix it in. In this way, the experts will not feel disturbed, making it easier to help new users. 2. It seems difficult for a novice to help the experts in establishing mutual assistance relationships. For example, new users can help high-hand code testing, or use the underlying library of experts to help them write some "superficial" upper-layer applications. But there are two gains: A newbie has the opportunity to access the highly handwritten code, and a master can be invited to solve the problem. Of course, the more perfect state is the loose Pair Programming mentioned earlier and the mentoring system in the 139 team.
Conclusion: being a good teacher can coexist and cause and effect each other. If you have been a newbie for many years and feel that no one is willing to help yourself or has never learned anything, you should reflect on whether you have done less.
