A better way to say this is that you need to rely on domain knowledge for how the application is structured. Contexts give you a directory structure that helps with a 1000 foot view of the system, and good naming strengthens this, but ultimately the finer details of “why is X here and not part of Y, and why does it talk to Z” is really domain knowledge that often leaks outside of the code itself over to this business you’re powering. So rather than a “weakness” I would say it’s a reality of any new team member coming into a project. The goal is instead of relying entirely on memory of passed devs, you have some architecture that screams its intent to help fill those gaps.
6 Likes
