Some principals in selecting open-source package/project
In a developers journey, they usually go through a phase where they are reluctant to use other people’s code. They rather implement it themselves if not under the project timeline’s pressure. This is not because they believe that they can do better, but rather they will not be bounded by the constraints that are introduced by the added dependency. At the end of the day, writing code is usually easier than reading. After this phase, develop may become more goal-oriented and not so focus on building packages themselves. Then selecting an open-source package/project becomes important. Below are some of the principles I apply when selecting an open-source project choose active package/project choose package/project where its lead has good communication choose the package/project that has a single focus Choose active package/project When importing a package/dependency, we are essentially starting a contract with the package. Future features and bug fixes update will inevitably affect the pr...