Recognize it and rock it. Meaning, don't be afraid to refactor it and take advantage of it. Of course you will end up having common folders, the trick is to ha

Recognize it and rock it. Meaning, don't be afraid to refactor it and take advantage of it. Of course you will end up having common folders, the trick is to have more than one and at the appropriate level. Sometimes you need a common folder between a few close-but-not-same components. Sometimes you end up deciding to reuse that common folder elsewhere, so you "promote" it up a few levels. Other names such as "shared" or even "service" can be used, as long as you put big related pieces in subfolders underneath. Recognize when things get messy with common folders and refactor then. This is the "trick", so to speak. You have to recognize "our common folders are starting to become a mess" as valid technical debt, because the team will keep having a progressively harder time finding the correct code.