DEV Community

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

Collapse
 
liviufromendtest profile image
Liviu Lupei

I don't want to be a buzzkill, but I think it's a good idea to look at this from multiple perspectives.

I would discuss this with the Manager/CTO to understand the potential ROI (Return On Investment) of that effort.

Building something doesn't cost you anything, but it's costing your company (since you do get paid).

I would also schedule a meeting with colleagues from other teams, to find out if they would use those components, or if they would like to build their own instead.

Maybe do a small POC and see if folks would actually use it or not?

Lots of developers are doing Résumé-Driven Development, doing things that would look good on their CVs, but that are not actually helping their companies or colleagues in any way. Don't fall in that trap.

If I would be doing something for "pure fun", I wouldn't do it on company time.

Most of all those big companies that contribute to open-source projects are also doing it for Marketing purposes (and obviously, they wouldn't publicly admit that, they're not that dumb).