Reflection on learning video tutorials

Reflections on learning video tutorials

I have read a lot of video tutorials, But I have spent a lot of time on them. But I also have some experiences. Let's write them here.

Video tutorials are of different quality in general. Good tutorials can always be refreshing, tools, techniques, ideas, and ideas (such as sundy lectures at the wheat Institute are excellent ). Poor tutorials always teach you how to use a knife to cut trees, and use cranky ideas instead of summing up questions. Instead of "Lao Tzu, this lesson will provide you with a function ", replace lectures with reading PPT, and teach people with stinks (a lot of junk tutorials like this on the Internet ).

A good tutorial is the best instructor for beginners: for example, when you are learning Android, you need to learn a lot of knowledge, including Java knowledge on Android Application Development and Android SDK knowledge, then there are a variety of eclipse skills, debugging skills, design patterns, software engineering, and so on. The instructor may not explain the whole story, but will pick out the key knowledge and explain how to find and use non-key knowledge. It will teach you some practical applications, not theories; it will write code in person to show you his hands-on programming habits. These are the most valuable experiences. Without this, it cannot be a very good tutorial.

In my eyes, high-quality tutorials must meet the following requirements:
1. Demonstrate your most valuable experience (such as start code writing and on-site analysis)
2. Give a general knowledge architecture to give everyone a general outline.
3. Teach you how to deal with the key points and non-key points, so that you can focus on it and reduce useless time.

After finishing the tutorial, you must also talk about how to learn the tutorial as a learner.

1. The first thing is in the preview stage:OutlineIf you haven't read this lesson, you have to preview it. You need an outline (Your own outline). If you have an outline, take a look at the outline first. If you do not have an outline, you need to sort out the outline quickly.
   Because excellent tutorials all have a feature of intensive knowledge. When your brain receives too much information, your brain's CPU starts to strike, entering anything at this time is a waste of time. To put it bluntly, it is not completely a waste of time. You have wasted time to broaden your horizons. Well, it is estimated that you will waste an hour = 5 minutes for someone else to search for information on Google.
   It must be your own outline. It is not an outline that has not been thought out by yourself. Drawing a general mind map is more effective than directly watching videos.
2. Next, when you watch a video: when you watch a video, you have to hold it in your hand.Outline supplement. The key point is from functions to implementation. Remember the functions. In mind, you must be able to simulate the situation when writing code. What code should you write? Make a draft or draw a draft on paper. If this is not done, the idea is not clear at all.
3. Next, let's talk about coding: Put the outline aside, encode it first, and think about these issues during the coding process. Can I compile the code smoothly? It must be smooth. Your words are misspelled. This low-level error is caused by a small amount of coding. Can you use a template to generate it? Why can the teacher write it smoothly, but I cannot do it? These code-related micro-operations must be well trained.
4. In conclusion, if you cannot describe the image of your things in a few words, it proves that you have not learned this part of knowledge. In other words, there are too few books to read and too many ideas.

It must be divided into 1234, so that it is clear. This should be the case for learning any operation. First, you need to understand the function (this is called understanding), and then write the code (this is called deep understanding and skillful micro-Operations). Third, we need to combine what you said before, and once again sort out the code writing process (a few words to describe, but when you think of these words, I have started to simulate the corresponding scenario in my mind ).

You must think about it more. Although Mr. Yang has a saying that there are too few books to read and think too much. However, it is not a waste of time to watch videos efficiently and adjust the video based on your own situation. "You have to watch more and think more!

For a person like me, I have read many teaching videos and many books. However, these are not very significant changes. It's like singing a song,

I have crossed the mountains and the sea, and also crossed the sea of people. Everything I have ever had vanished like smoke.

Sometimes, when you want to do something, you will find that Lao Tzu's reading so many videos is useless.
Then you sang

I was lost, disappointed, lost all directions until I saw ordinary is the only answer.

Haha, of course. I am not talking about this song. Let me use the songs to express my feelings about not making any breakthroughs after watching the video tutorial.

The reason is that the reflection capability is too poor and there are too many videos, but have you summarized it? Why are you so inefficient? Can you blame the teacher?