Ask HN: Libs between teams or not?
1 comments
My former workplace maintained a "common code" library that almost every team in the company used. I think the key is to strike a balance between functionality and compactness. If you're gonna impose standards, don't make them hard to follow. Document everything and make sure it's clear when/when not to use it.
We basically have two camps: one camp who haven't done this before and think it's a great idea.
The second camp seem to have more experience and are very wary of the complexity of managing dependencies and creating bottlenecks.
I would like to invite to a discussion on the topic. What are yoyr experiences and what would you recommend?
Many thanks.