Pay attention to the primary knowledge

Now under the Internet environment, pay attention to the rational knowledge learning programmer less and less, especially in this kind of training institutions under the environment of the big bang, you will often see something like three months on the Internet from entry to master the high concurrency, distributed AD, I believe that the training organization has the ability to this technology, but I do not believe a beginner is such a good capacity. There was even an architect born in 1997 who became an architect in his early 20s among the lecturers in a training institution. In my mind, architects are not learned, architects are fed through projects. Well, let’s get down to business.

Why should we focus on fundamental knowledge? Since primal knowledge is our root, I have given three examples to illustrate this view.

1. You know design patterns. Whether you’re doing system architecture or reading the source code for open source projects, you’ll find that in the end they can’t get around design patterns.

2. You understand data structures and algorithms, and you know how to prioritize lists and maps in high-concurrency scenarios where every second counts and time is money.

3. Your understanding of the principle of network communication will be of great help when we do system architecture and problem elimination.

It can be said that primal knowledge determines the lower limit of programmers. Programmers with strong primal knowledge will not have a lower limit. On the contrary, programmers with weak primal knowledge will not have a higher limit.

02. Build your own core technology stack

There has always been a midlife crisis among coders, even those who have not yet started, who know that programmers only work until they are 35. I’m not going to get into the “yes” or “no” part of this argument. I’ll leave it to time, and when you’re 35 years old, the answer will come. Most programmers have a sense of mid-life crisis, so in the beginning, they will spend more time to learn. Many people will have problems in this place, it seems to spend a lot of time in learning, but there is no progress or even relatively backward, why?

A lot of programmers, including me, learn this way. Now that big data is so popular, buy a book or watch a video to learn about it. After learning for half a month, big data is too difficult to learn, so let’s put it on first. Hey, this recommendation system seems very interesting ah, and buy a book to learn. In the end, there is a cycle where every skill is learned and every skill is an entry point. It seems to know everything, but when you do it, you know nothing. That’s the magic.

This is a cycle that many programmers jump into. For programmers of this kind of technical work, this is a taboo to learn, because there is no advantage in the technical industry knowledge is broad relative to deep knowledge, in the company dedicated to do specialized work, need is technical depth. So each programmer needs to build his or her own core technology stack. If you are involved in Java Web development, you will have more knowledge in a particular direction, such as high concurrency, messaging middleware, or distributed architecture, than the other programmers in the company or around you, which will be your capital for promotion, salary increase, or career change.

Be a self-driven employee

There are two kinds of employees in the workplace, one is task-oriented employee, the other is self-driven employee. Task-oriented employees, when the leader arranges a job, they just finish it, never thinking about whether the function I wrote could be optimized. Task for task’s sake. This employee is stuck in the comfort zone, and it’s hard to find a place to live when the comfort zone is gone.

The ego-driven employee, on the other hand, asks himself, at every turn, what is the root cause of the problem? Why does this happen? How can I avoid this kind of problem again? For each problem, he will find out the root cause and provide the best solution.

For every technology the company uses, he tries to understand the rationale behind it. What are the application scenarios? The pros and cons and so on. For the self-driven employee, the root is the final answer.

Self-driven employees are more likely to do business with their own thinking, to get to the bottom of technology and pursue principles, which will be a happy process. After thinking more, they will find the correlation between scenes and principles. The growth of self-driven employees is relatively fast, and they will have their own core competitiveness in a short time.

04. Take notes and blog

Note-taking, blogging, summarizing and sharing is something that everyone should do, not just programmers. Note-taking is a summary of your past and a way to record important things you’ve learned so you can refer to them later. As the old saying goes: It’s better to have a good memory than a bad one, and it’s always good to take notes.

Blogging is a process of sharing, sharing your knowledge in the form of words may help a lot of people, this process is happy. Blogging is also a great way to fill in the gaps in your body of knowledge and refresh your knowledge as you go along.

The last

Play a small advertisement, welcome to scan the code to pay attention to the wechat public number: “Technology blog of the flathead brother”, wonderful tweets not bad, learn together, common progress.