I have a _perfect_ example of this.
very often development teams will value re-use and dry to the point that they'll conclude they need to stuff most things into a common library and share it amongst all their codebases.
Anyone who has seen this done long term has seen this accrete until everyone is afraid to change the common library for fear of breaking _everything_.
IOW, the risk profile of something like this grows over time. It starts out small but each time a project adds it as a dependency the risk grows.
and yes, I understand everyone is going to post about versioning and change management and all the myriad ways one can try and mitigate this.
the point here is that when using a common library like this you must be circumspect in what you put into it. The risk threshold for it being worth going into this common library is going to be much lower for someone who pushes for a common lib and then skips to the next job vs someone who was there over the next 3-5 years and personally experienced the pain and fear such approaches invoke longer term.
and to repeat myself since I know this is HN.
No one is saying you can never have common libraries like this, what's being said is that the long term risk is much more likely to be respected by someone who long term experience and therefore that person with long term experience is much more likely to be able to design a system that can be worked on productively over the long term.