> often I find unused gems they are afraid to remove them in case it actually is being used, I've worked on code-bases of small to medium size where people wer

> often I find unused gems they are afraid to remove them in case it actually is being used, I've worked on code-bases of small to medium size where people were afraid to remove self-written code because nobody knew if the code is actually called somewhere. It's not actually the gem that's the problem - it's being diligent. If you need a gem's function add it as top level dependency, don't rely on some other gem depending on it. require the code explicitly everywhere you use it. That way you can at least search your code base for it. Be equally diligent when removing code: Remove all code that only this code depended on. Other than that: Don't be afraid to break stuff.