When learning new technologies, in order to avoid being misled, first, read official examples, such as JAVA’s pet shop or .NET’s pet shop. But later I realized that we can’t learn like this. Because I am unfamiliar with new technologies, and the code I started using is this, then the style of writing programs in the future will often be like these examples. In fact, when we write business applications, we do not need such an architectural style, nor do we need to show so many code patterns. Drawing pictures of cats and tigers makes us very tired, and it cannot change the inherent thinking. We don't need this beautiful-looking code.
The second way to learn new technologies is to find an open source system on the Internet. For example, some early adopters of new technologies have developed a forum system or some other management system. But this method also has a drawback, that is, the code he writes has his own style, and he is still in the trial period. He may write this to learn this technology, rather than to develop this management system. Originally, we were just a blank sheet of paper when it came to new technologies, but now we were led into a ditch by him.
The third way to learn new technologies is to read the source code of the new technology itself. Unfortunately, I was not familiar with the new technology, and the source code of the new technology itself was even more complicated. I was confused, struggled to see any progress, and wanted to give up.
Therefore, to learn new technologies, it is best to learn third-party foreign open source source code based on new technologies. They have a quick and in-depth understanding of new technologies. They apply new technologies not to try new technologies or to show off new technologies, but to complete one of their practical products.