When people debate whether to use mono repository or multiple repositories, they usually focus on how fast builds are, continuous integration/continuous delivery (CI/CD), or headaches related to dependency management. But the real story is bigger than code. Conway's Law says that the way teams talk to each other affects the systems they build. This includes how we organize our repositories.

In this talk, I'll show why mono-repos get a bad reputation and how looking at them through the lens of Conway's Law can change that. We'll use real-life examples to show how the way a team organizes its repositories (a repository is a collection of files, like source code, stored in a computer system) reflects how that team is organized. We'll also discuss why getting this alignment right can make it easier for teams to work together and get things done more quickly.

You’ll walk away with a fresh way to think about the “never-ending debate”: not just about tools and pipelines, but about people, culture, and the way we work together.