DEV Community

Discussion on: Should I write my own lib for a work project?

Collapse
 
mrdulin profile image
official_dulin • Edited

Don't use the company's project as your playground. For generic packages, don't reinvent the wheel unless you can maintain it for a long time. In more cases, based on the existing package, according to the company's business and development efficiency needs, we should encapsulate some business logic using the open source package . But sometimes this kind of encapsulation is unnecessary, and additional code will be introduced, which is not conducive to troubleshooting fundamental problems, and the granularity of open source package encapsulation is sufficient.