I just read the first half, and gave up. No offence, I agree that we should rebuild more than we add. But this just smells of naivety: > Library that does some

I just read the first half, and gave up. No offence, I agree that we should rebuild more than we add. But this just smells of naivety: > Library that does something horrible that all your software depends on? Turn off the horrible behavior and remove your dependency on it! Oh great o removed all my dependencies of a horrible library and now my project has 0 lines of code because "all your software depends on". Now I'm on a multi sprint crusade to, instead or removing, I'm replacing it. And since I had so much energy from this suggestion, I keep making mistake after mistake because I'm blindly removing stuff that I don't understand, costing my team valuable development time. Maybe a better way to say this is "analyse you dependencies, see what you can improve, draft a plan on the high level changes that need to be done, prioritise the changes according to all the other stuff you need to do". Seems like the OP just wrote this right after/while being extremely annoyed. No an awful issue, but it clearly shows a bit of lack of planning.