I entered yesterday to my new job and while browsing their repositories, I noticed they have a project for every resource of a REST API. For example, if they need to add a REST resource called "people", they proceed to create a whole new repository that contains only the endpoints of the resource "people".
Honestly I've never seen something like this before and I can only see downsides of this design, for example for every piece of reusable code, they just copy and paste it multiple times across the projects that are part of the REST API and sometimes they make a library and share it across the repositories. Even with the library approach I think this will be a mess to deal with. Am I wrong? Does this design provides any advantages?
Currently there is only one maintainer and he is on vacations so I need to wait for the next week to ask him about this decision.