I completely agree with the modular, single purpose library approach, but, for large teams, it adds a lot of hidden overhead: library curation. It's so easy to

I completely agree with the modular, single purpose library approach, but, for large teams, it adds a lot of hidden overhead: library curation. It's so easy to just, `npm install` or `bower install` a new library, sometimes you don't even think about it. But, this causes a huge bloat and duplicated functionality that both produce huge build artifacts and increase the learning curve. You need to make sure you have at least one person dedicated to saying, "I know B does X better, but, we are already using A and it does X good enough."