Shulou(Shulou.com)06/01 Report--

This article mainly explains "how to learn Spring Security". The content in the article is simple and clear, easy to learn and understand. Please follow the editor's train of thought to study and learn "how to learn Spring Security".

1. Systematic Learning 1.1 Why systematic Learning

Why do we have to learn systematically? Whether you do IT or not, there is a need for systematic learning.

Systematic learning of a knowledge point can make us think more comprehensively when we encounter problems, which is also a characteristic that a mature engineer should have; fragmented learning is easy for us to draw some one-sided and even wrong conclusions.

However, systematic learning takes a lot of time and energy, and some people may think it is not worth it, so they give up systematic learning and believe in copying and pasting to change the seven-character mantra and plunge into the bitterness of CURD.

After work and chat with friends, I also found that many people understand the harm of CURD every day, want to improve, but do not know where to start? Brother Song told you to start with systematic learning.

1.2 systematic learning how to cut into

Many children do not know where to start systematic learning. Let me give you a simple example:

The company wants to build an email server with RabbitMQ, but you have never used RabbitMQ, so what should you do? Things are urgent at work, so it is generally possible to do this:

Search a tutorial on the Internet and do it from beginning to end. It's a success. The job is done. If you are not successful, search for another tutorial to do. Now there are so many online tutorials, there is always one suitable for you.

When the problem at work is solved with the help of online tutorials, RabbitMQ is thrown aside and doesn't care anymore. If something goes wrong, continue to search.

I believe this may be the daily life of most of my friends. If you want to learn systematically, this is a good starting point, please continue to read:

If you buy a RabbitMQ-related book in your spare time, or go through its official documents in your spare time, and seriously study its message queue, message sending and confirmation, fault recovery, failover, REST API operation RabbitMQ, monitoring, performance improvement, and so on, and carefully read it from beginning to end, then the next time you encounter RabbitMQ-related requirements, writing code will come in handy. Because you already know what features RabbitMQ has and what functions you can achieve, you don't have to search Baidu over and over again.

In fact, in our daily work, there are many entry points for systematic learning. When you encounter a problem when you Coding, Baidu search, copy and paste to change it, and do not go deep into what the reason is, this time actually missed an opportunity for systematic learning. In fact, at this time, you can think about why this is the case. if you dig deep from the current problem, there will be a surprise.

Some friends say that they are too busy at work and have no time for systematic study. In fact, it is very difficult for me to give you any good advice. I can only say that there will always be time squeezing. I am the kind of person who is hard on myself, so I basically don't have this problem. No matter how busy I am at work, I have time to study, but my way may not be suitable for everyone.

two。 How to start a new framework

In general, there are several ways to choose from:

Watch videos / online lessons / read books / read blogs on the official website

Some people do not know which way to learn better, or which way to choose. Brother Song is here to give you a little analysis.

Video tutorial

Advantages: you can get started quickly and understand the specific application of this technology in a short time. Disadvantages: watching video is more time-consuming, so we can see that the major video websites generally have the function of double-speed playback.

Read a book

Advantages: the knowledge in the book is systematic, which can help readers build a complete knowledge system about a knowledge point; at the same time, reading a book can also have a deeper understanding of a certain knowledge point. Disadvantages: books generally have a little lag. After all, it takes time from writing books to publishing houses after the knowledge points are out. On the other hand, for beginners, they may not be able to understand when they choose to read books directly.

Look at the official website

Advantages: the official website has the same advantages as books, and is more real-time. Disadvantages: in most cases, the technical official website we learn may be in English, so there are certain requirements for the readers' English proficiency; on the other hand, although the introduction of the official website is complete, it is relatively simple and lacks some practical experience. from this point of view, books incorporate the author's experience in the use of technology, which may be better.

Read the blog

Advantages: blogs can access the latest technology, and access is extremely convenient, most of the technology sites online are filled with a large number of blogs. Disadvantages: most blogs present fragmented knowledge, which is not conducive to the establishment of a complete knowledge system.

After understanding the advantages and disadvantages of each approach, let's take a look at the learning steps:

It takes a little time to get started quickly, but it's the most effective way to get started (skip this step if you have a lot of experience in development, or if you can understand it directly by reading a book). Read the book / read the official website to study deeply and fully explore the systematic characteristics of the book. Read the blog for the latest developments in the technology.

In this way, we can learn a certain knowledge point systematically, and then gradually establish our own knowledge system.

3. When is the right time to look at the source code?

There is also an issue that everyone is more concerned about, that is, what do you think of the source code? When is the right time to watch it?

Let me also talk a little bit about experience in this area.

First of all, it is not recommended to try to read the source code as soon as you come up, which is a bit time-consuming.

For source code reading, it is recommended to adopt the method of "rural areas encircling cities", that is, "point movement into a line, line action into a plane". When learning, first learn the application of a certain technical point, and then, combined with specific applications to analyze the relevant source code. this way the source code is much easier to read. This piece you can refer to my recent serial Spring Security series, basically in this way, each time after a knowledge point, I will take you to take a look at the source code, at this time the source code does not look boring, very interesting.

When we conquer the source code of a knowledge point, and finally look back at the source code as a whole, you will find that it is so simple!

Thank you for your reading, the above is the content of "how to learn Spring Security", after the study of this article, I believe you have a deeper understanding of how to learn Spring Security, and the specific use needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.