Learning topics for: Feynman learning and show me the code

Recently caught in a confusion, that is, the time for an interview, learned a lot of things can never remember or not remember exactly, so the concept of representation when needed, and not well expressed. I carefully analyzed what should have two reasons, one is language skills, and the second is the mastery of knowledge itself.

In particular, I would like to extend a second point for reflection in order to form its own set of learning methods to aid their grasp knowledge. I have always believed Qinnengbuzhuo, but I believe there is a learning methodology, there is a shortcut, and sometimes better than the blind method is more useful effort.

I understand Feynman learning

Recalling their previous learning career, in fact, I often use "Feynman learning", but at that time he did not understand it was a more scientific approach to learning, often their own time to think about the nature of a problem, then the problem answers come out and repeat the process, or explain to others about, or personally go to practice, to get a feedback, which play Network access, consolidate the role of knowledge.

It may be directed in recent years in terms of learning, but I gradually neglected to learn, but immersed in a variety of information flow, the lack of independent thinking, lack of feedback and practice. In this era of information explosion, attempted to use the brain to memorize all of the information, it is almost impossible. Even conscious effort to shield some useless information, deliberately to keep in mind since that information is also very important to do, because there is no practice and feedback. Remember the "deliberate practice" mentioned in the book, we do have a sense of training, but also to keep training and feedback to be able to form a complete thought or knowledge structure curve. This is how it is, what we need is to form a closed loop of knowledge, rather than accept the one-sided information, because the information is not that kind of knowledge into their system.

Think about it, Feynman learning method should be useful, I tried to read his previous blog, the content was telling often when deep into the details, and have their own thoughts and insights, so for something before also memory can make a difference. Later, the blog slowly turned into a tool for recording information, and attempts to use blog to record the knowledge, and the liberation of the brain, although to some extent it is useful, but often just the opposite, because a lot of things did not go through thinking, but a simple copy and paste, terrible is considered to have mastered the knowledge of self, played the role of a self-moving. I think this is probably caused by one of my main reasons vague knowledge of the memory of it.

In conclusion, that is, in their own learning process, think of something less, something more than copy and paste, partly because the development of the Internet, over-reliance on its own network to solve the problem. On the one hand it is the limits of knowledge, after all, when in the underlying structure of knowledge, it is difficult screening correctness upper content. That is, do not understand the content, you can not judge the rationality. This time the book should be a good way to understand the information, followed by the official website, followed by the professional blog, and finally ordinary Bowen.

Mentioned earlier software development is an implementation detail, not a knowledge. This implementation details for developers is very unfriendly, because the technology has been in finer iteration, the implementation details have been transformed, developers have to constantly spend energy to get to know these details, because if do not understand the implementation details of the case, is not software development. And these implementation details for a platform for a tool might not work anymore. Private thought, developer core competence should be learning, problem-solving way of thinking, there is a solid professional foundation. These aspects is what I have been trying to enhance the ability of.

Talk is cheap. Show me the code.

The above talked about so much, in fact, just thinking about methodology. In fact, Linus Torvalds of the phrase "Talk is cheap. Show me the code" was more intuitive, what can you say count, I look at the code words really real, the reality is this, can represent a person's not that works well, compared to what I would do something more useful is that I have done something.

Code is a basic ability to staff development, not pay attention to what bells and whistles in the software industry, it has the ability, not the ability on the next, this is a real and cruel fact. So write some useful code, and less from some useless chicken soup. My personal plan is also true, if you later try to write articles, then attach the code, full details of the content. Generalities and does not have much meaning.

the above.

Guess you like

Origin www.cnblogs.com/small-world/p/11407609.html