Increase your productivity! Use it directly without having to re-develop it, saving time. BUT packages also have side effects. Each package has some dependencies. If a dependency is updated, problems may occur. When a problem occurs, you have to solve the bug, which is a very worrying problem.
Reinventing the wheel does not make much sense, unless your wheel is more advanced than others, then you can also open source it and help more people. This is the fun of open source. Using various open source packages can greatly reduce the development cycle. Many excellent open source works can improve the performance of the project. But this does not mean that the skill requirements are low. We need to understand the advantages, usage scenarios, and even read the source code of various open source libraries. Not all packages that implement functions can be freely cited for use in projects. I am a novice, a porter of github ^_^...
There are still requirements. First, you have to find a reliable package/plug-in. Unreliable plug-ins will introduce all kinds of inexplicable bugs. In the end, don’t you have to fix it yourself (ca) (pi) and (gu)? Secondly, you must at least understand the general writing method. Firstly, it can be used in debugging scenarios. Secondly, it can also improve your own skills (did you think that you are the only one who can find wheels and others can’t? They are all like coding building blocks). The value of this level is low on the street, and now it has basically fallen into the red ocean); thirdly, there are often a lot of packages in large projects. Are there conflicts and dependencies between them? How to effectively improve performance? You will understand when you suffer a loss...
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
Reduced wheel-making
The prerequisite for using a bag is that you must be able to understand it
Increase your productivity! Use it directly without having to re-develop it, saving time. BUT packages also have side effects. Each package has some dependencies. If a dependency is updated, problems may occur. When a problem occurs, you have to solve the bug, which is a very worrying problem.
Reinventing the wheel does not make much sense, unless your wheel is more advanced than others, then you can also open source it and help more people. This is the fun of open source.
Using various open source packages can greatly reduce the development cycle. Many excellent open source works can improve the performance of the project. But this does not mean that the skill requirements are low. We need to understand the advantages, usage scenarios, and even read the source code of various open source libraries. Not all packages that implement functions can be freely cited for use in projects.
I am a novice, a porter of github ^_^...
Everything that comes out of the bag will eventually become shallow, so you need to know how to do it.
There are still requirements. First, you have to find a reliable package/plug-in. Unreliable plug-ins will introduce all kinds of inexplicable bugs. In the end, don’t you have to fix it yourself (ca) (pi) and (gu)? Secondly, you must at least understand the general writing method. Firstly, it can be used in debugging scenarios. Secondly, it can also improve your own skills (did you think that you are the only one who can find wheels and others can’t? They are all like coding building blocks). The value of this level is low on the street, and now it has basically fallen into the red ocean); thirdly, there are often a lot of packages in large projects. Are there conflicts and dependencies between them? How to effectively improve performance? You will understand when you suffer a loss...