What should I do if I encounter new knowledge at work?

We always say a word that we always say, but it is not so easy to learn at work. In the face of new knowledge at work, the average person often first fears, then complains, and then does not feel confident. Finally, he finally draws the conclusion that he is not the only choice. In fact, there is not much difference in intelligence between people. What is lacking is just a little bit of method and confidence. This outsourcing has encountered new knowledge that you have never touched before. Here, I will share my feelings about learning or my approach to new knowledge, hoping to help readers in their future work.

View help documentation

Do you still remember the help we saw on the lake Daming? : If you do not know anything about B, check the help first! After so many years of study, have you lost what you learned on the first day of the advanced training? Whether it is learning frameworks or learning software, help is the first giant we should think of. In fact, framework or software authors have already poured all the words they want to say to you into help, in other words, the help document is the most effective and fast way for us to communicate with the author. Help is the greatest grace given to us by developers or our predecessors.

Taking the dinamica framework we have been using this time as an example, there is very little information about this framework on the Internet, and there are just a few official documents, and since the developers of this framework are Spanish, so most of the documents are in Spanish (tragedy )! Although most of them are in Spanish, there are still some in English. It was my idea to "read the English first", and I had a basic understanding of the framework after reading it.

Never forget to stand on the shoulders of giantsOf course, when looking for giants, we should not just look at help documents. All resources on the Internet are for help, such as others' blogs, such as enthusiastic friends in QQ groups or forums, these are giants. Help is only the most common among giants.

Macro view of new knowledge

Taking the new framework we encountered this time as an example, when looking at other people's code, we should not open class files, and then drag them in at one end. Because that will only let you jump from one method to another, and jump from one class to another. The final result is to make yourself confused, and then give up. The conclusion is that none of them can understand what people are doing. In fact, this is not the case. Looking at the source code requires a skill, and it is never necessary to get in!

First, we should look at the functions of a class as a whole. Then we can see that this class has several methods and several variables, this class, its methods, and variables are determined based on Annotations and naming. The source code can be viewed here for the first time. Do not go to the method. The most taboo is to press Ctrl + the left mouse button to enter the method! The ghost knows which method of the class to jump to when the mouse clicks to the end. The real idea of the functions of a class is the future. At the beginning, we only need to look at the class variables and methods from a macro perspective. This is enough. I personally think that the specific implementation of methods in the research class should be done only after being familiar with the entire framework. At the beginning, we should temporarily give up the details and focus on macro functions, only in this way can we ensure that the source code is not dizzy.

It is worth mentioning that eclipse has paved the way for us. The outline (outline) in the eclipse view clearly shows the class methods and variables at a glance. Look at the source code. If you don't need the outline view, it's like a word from the boss in the dark temple: "You are searching for death !"

You may not know the scenery on the side of the road, but you must know where you are now!

Starting from existing knowledge

After reading the help, I had a macro view. Finally, I started to study the principles of new knowledge based on my existing knowledge. For example, if we have learned SSH, where should we start when we encounter a new framework? Looking at help, there is a macro that has been done, so the rest is to start with the existing knowledge, and he has his own foundation for the framework (the Framework doesn't appear out of thin air ), in Java, most of the frameworks support J2EE, so the first thing to note is web. for the XML file, you need to check how the configuration allows the program to find the framework in the XML file. Servlet or filter, which we are familiar with, should be just a little bit from here to the depth of the framework to explore his mysteries.

For another example, we learned about SQL server. If we encounter a new database, it may be Sybase or postsql. It is natural to find the same point as SQL Server, and then find their differences in the Process of reuse. Sybase is similar to SQL Server, but there are some differences between postsql and SQL Server, such as tablespaces, schemas, and roles that are not in SQL Server, these are what we need to learn in the comparison process.

The Foundation is very important. The foundation + method is the main factor determining acceleration.

Improvement is necessary, learning new knowledge is indispensable, just as the ancients said, "Ask the channel which has to clear such, for a source of live water ." There is a way to control the living water. It is never busy, blind, or reckless!