What to do when new knowledge is encountered in work.

It's not so easy to learn at work when you're always learning what we often say. Most people face the new knowledge in the work often first fear and then complain and then not self-confidence finally fled, concluded that he is not this piece of material. In fact, there is not much difference in intelligence, the lack of a little bit of method and confidence. This outsourcing encounters the new knowledge that I have never contacted, here to share the feeling of learning or the method of treating new knowledge, hoping to play a useful role in the future work of the reader. See Help documentation

Do you remember the help we saw at Daming Lake? : b What do not understand the first to see Help AH. Have you been studying for so many years that you have lost the first day of your study in accelerated? Whether learning the framework or learning software, help is the first giant we should think of, in fact, the framework or the software authors have put all they want to say to you in the help, in other words, help document is our communication with the author of the most effective and fastest way. Help is the greatest grace that a developer or predecessor has for us.

Taking the Dinamica framework we contacted this time, there is very little information about the framework on the Internet, there are so many official documents, and since the developer of this framework is Spanish, the documentation is mostly Spanish (tragic). Although most of them are in Spanish but English is still there, "first to read the English" is my idea at the time, and sure enough, after reading the framework has a basic understanding.

always do not forget to stand on the shoulders of giants, of course, when looking for Giants, not only limited to help documents, all the resources on the network is to help, such as other people's blog, such as QQ Group or the forum's enthusiastic friends, and so on, these are giants, help is only the most common giants. to see new knowledge in a macroscopic way

Also take the new framework of this encounter example, when looking at other people's code should not open the class file, and then go in. Because that would only allow yourself to jump from one method to another, jump from one class to another, and the final result is to see yourself disoriented, to make yourself foggy, and then give up. The conclusion is: the other people's things are cattle, see not understand. In fact, it is not so, look at the source code needs skills, not to go into the look.

You should first look at the function of a class as a whole, and then see how the class has several methods, several variables, judging by the comment and the name of the class and his various methods, the variables are roughly what. First look at the source to here already can, do not go to the method inside, the most taboo is CTRL + mouse left button into the method. The ghost knows the mouse point to point to a point to the end will jump to which method of the class. The real thing about the function of a class is to figure out what's going on, and it's enough to start with a macro-based look at the variables and methods of the class. Personally think that the study of the methods of the specific implementation should be familiar with the entire framework after the first time, the beginning should give up the details, focus on macro-function, only in this way can ensure that the source is not dizzy.

It is worth mentioning that eclipse itself is the groundwork for us, the Eclipse view of the outline (outline) gives us a clear display of the class of methods and variables, at a glance. Look at the source code if you do not use the outline view as the boss in the Dark Temple: "You are suicidal." ”

can not know the roadside scenery, but must know where you are now. starting from the existing knowledge

Look at the help, with the macro, and finally from their own knowledge set out to study the principle of new knowledge. For example, if we learn ssh, where should we start when we encounter a new framework? Look at the help, there is a macro has done, then the rest is to start from the knowledge already, for the framework he always has his own foundation (frame perception is not out of nowhere), in Java most of the framework is to support the EE, So the first thing to be aware of is the Web. xml file, to see how it is configured in the file to let the program find the framework. Servlet or filter also good these are familiar to us, we should just from here to a little bit to the depth of the framework to dig his mystery.

Again, like the database, we learned that SQL Server may be a new database if it is Sybase or postsql it is natural to find the same point as SQL Server, and then use the process to find their differences. Sybase is broadly similar to SQL Server, but there are some differences between postsql and SQL Server, such as tablespaces, patterns, and roles that are not in SQL Server, which we need to focus on during the contrast process.

Foundation is important, the basic + method is the main factor that determines acceleration.

Improvement is necessary, learning new knowledge is indispensable, as the ancients said, "Ask the canal which is clear, for the Fountainhead to come." "And this is a way to harness living water, not to be busy learning, blind learning, and reckless learning."