> there is no relevant difference between a member of my team utilizing that class (from within the same module) and other people using it (as a library I have

> there is no relevant difference between a member of my team utilizing that class (from within the same module) and other people using it (as a library I have published). The difference between a team member and a library user is that the team member works in the same project while library users have their own projects. So if you change something inside the class, you can change all the uses of that class in your project but you can't change other people's projects. That's why I added the clarification, because there is a very obvious reason to be strict about the API of a library that other people use: you can't change those uses.