In my most recent project, we've been using a single Git repo for all the apps, services, and shared libraries we built: the so-called mono-repo architecture for source control. For me personally, that was a first. So I learned a lot about how a mono-repo architecture affects dependency management, facilitates refactoring efforts, complicates CI/CD processes, and so on. In this talk, I'll be sharing those lessons with you. Among other things, we'll discuss why proper code organization greatly helped us managing our mono-repo, we'll uncover both the benefits and complexities that come with evolving shared dependencies in a mono-repo, and much more. For technical details, we'll use Azure DevOps and Azure Pipelines as references during the talk, but the generic concepts are applicable for any proper CI/CD toolset. So to everyone interested to learn how repository architecture affects developer workflow, this talk is for you!