I've learned my lesson trying to structure "large projects" inside of a single "project" or logical repository. A developer I hired at one point had read an ar

I've learned my lesson trying to structure "large projects" inside of a single "project" or logical repository. A developer I hired at one point had read an article written by someone in the OSS community promulgating the virtues of treating your "projects" like OSS projects and if you have a "large project" breaking it down into smaller constituent projects with their own source repository, dependency defs, README's, tests, Vagrant / Docker environments etc... This fits well with the ideas behind small composable units of work and it also increases clarity. [EDIT] Essentially, if you have a large project, it's probably time to re-think how you're coupling or de-coupling functional units. The goal being lots of small, documented, and tested units composed to create a "large software product".