> Isn't "find all usages" a pretty basic feature in modern IDEs? If you're working in a single self-contained codebase this really isn't very hard to do. Not a

> Isn't "find all usages" a pretty basic feature in modern IDEs? If you're working in a single self-contained codebase this really isn't very hard to do. Not all "find all usages" are created equal. Here, the language is very significant. In languages where there is more than one way to use something, this becomes more complicated, with more corner cases to keep in mind. In languages where there is only one way to do something, this is less complicated. > IMO a lot of the teaching around best practices in OO programming doesnt differentiate enough between things that matter in authoring libraries versus self-contained proprietary code. When everyone is committing to the same repo certain types of encapsulation and abstraction aren't always as critical as they're made out to be. This isn't a matter of library/proprietary code. This is a matter of scale.