5 ms·
> Dependencies kill teams Do you mean that when you have structured the organization so that each class is worked on by at most one team, you want to reduce th
by robalni 4y ago
> Dependencies kill teams
Do you mean that when you have structured the organization so that each class is worked on by at most one team, you want to reduce the number of dependencies between classes in order to reduce the number of dependencies between teams?
> they have to consider all possible points of entry
So is this basically what I mentioned, that you want to reduce the number of places you have to look in when you want to find all uses of it?
- kerblang 4y agoTo the first question: By "dependencies kill teams" I mean all the forms of dependencies: Database dependencies, web service dependencies, library dependencies, across teams, across organizations, and so on. Arguably internal dependencies inside a program are the least lethal. You are largely doing others the favor of implicit documentation by using scope control, a guaranteed statement of "This is never used outside this file". They might be able to figure as much out by grepping, remove & recompile, or IDE-based tools. "Greppability" is often part of the solution when dealing with database & http dependencies. As for the second question, basically, yes.