You’ll take away the most from this talk if you have a basic understanding of revision control.
While having a separate git repository for each project is the most common way to do version control, there is also the opposite approach: a single, “monolithic” repository that contains the code of all projects of a team or even of a whole company. Although this might sound like a terrible idea, not only small development teams but also huge IT organisations like Google or Facebook report great success running a mono-repo.
In my talk, I’m going to highlight the pros and cons of both approaches and tackle the question of which is the superior one. The answer will surprise you! ?