Do you learn when you are interested, or do you become interested only after you have learned?

At first glance, this problem is exactly the same as the chicken or the egg problem. It seems unsolvable, but the truth is not far from you and me. I think it is very meaningful to think about this issue. At the end of the article, I will mention how it will help you to figure out this issue.

For me who just graduated, I seldom learn the bottom layer, only how to use tools, such as Redis. Recently, I re-learned Redis and its bottom layer, learned the source code, and learned the exquisite design of its data structure, which made me deeply appreciate the beauty of data structures and algorithms. In the class, the teacher read it according to the PPT, but it was really not interesting. I once heard from Geek Time [Left Ear Mouse] that programmers should pay attention to some things that haven’t changed in 10 years, such as data structures and algorithms. Today, I learned Redis and realized this deeply. This will help me in the future. The technical learning has a certain guiding significance. What are the basic technologies listed by the big guys as I posted below?

It is estimated that many students should be the same as me. They are pre-exam assault players. This type of players has a shortcoming, which will be forgotten after learning. After this semester, it is very good to have 10% left in the next semester. up. You are very clear about whether the foundation is solid or not. You can go to LeetCode, or go to some famous OJs to write questions to test how well you have mastered the data structure and algorithm.

My situation is not much better. I didn’t start to study LeetCode questions until April 21 when I was looking for a job in my junior year. When I study questions, I will have a deep understanding of some data structures, know how to use them, and which one to use under what circumstances. data structure. Why did I mention the detection method of brushing questions, because I think school teachers are basically not good at teaching you how to write code, just talk about the characteristics of a certain data structure; another point, I think what schools should pay attention to is that they should give examples Let’s talk about the use of a certain data structure. This example does not need to go too deep. What are the application scenarios of this data structure, which famous framework is used, and it is used very well and wonderfully. The author of Linux once said a word, Talk is cheap, show me your code, which also shows the importance of coding, and getting started with code is the best choice to master the data structure.

Back to the topic, then to learn programming, or to learn any skill, should you learn it only if you are interested, or only after you have learned it? My answer is the latter. If you don’t learn it, you won’t experience the fun. If you don’t experience the fun, of course you don’t want to learn it. If you don’t learn it, you won’t experience the fun. This is the same as the thread deadlock we learned, forming internal friction up. The solution is to learn, and it will happen that I still can’t feel the fun after learning. I always believe that it’s because the person who teaches us makes me not feel the fun, not because the course is boring. Take Redis today as an example. When the teacher talked about the underlying principles, the underlying data structure, ziplist, quicklist, sds and other data structures, I deeply realized that the data structure I learned is not deep enough, because the Redis class is not deep enough. I can tell you about the data structure. This gave me the idea to learn the data structure again, and I really want to find out how the bottom layer of Redis accesses the data, which I call interest. Figuring out the data structure, in turn, will give me a deeper understanding of Redis, and the two complement each other. Just because learning Redis involves the knowledge of data structure, one knowledge system is connected to another knowledge system, and if you don’t understand the basic data structure, you can only be an engineer who calls Redis API. So I can understand what [Left Ear Mouse] said, so I should learn some basic technologies in depth. Do you want to die on data structures and algorithms? My personal opinion is that after you have some foundation, when you learn other frameworks, things you haven’t understood are used in it, and you will look back and make up for it. Gradually, you will have a more comprehensive and in-depth grasp of the basic technology.

Recently, I have a new feeling, that is, high school students think that undergraduates have a lot of time, and undergraduates think that graduate students have time, but in the end they all find out that they are actually quite busy. When I got to work, I thought that no one would take care of me, and I would be fine after finishing the work, but I found that I still didn’t have much time to study, work overtime, and use Douyin all night. I once heard the boss talk about his own experience , He said that he couldn’t read books anymore after he was 30 years old, and told me to learn things and read books as soon as possible. Just in response to that sentence, black hair doesn't know how to study early, and Bai Shoufang regrets studying late.

The learning process is very hard, and when the harvest comes, you will experience that kind of happiness, the feeling of mastering things that truly understands a technology, and that feeling is beyond the reach of others! Imagine, during the interview, slapping the interviewer and getting a high salary! Friends, let's all study!

Hope this article will be helpful to you!

Guess you like

Origin blog.csdn.net/liuzr_/article/details/128662361