I would advise doing this on a class basis if you are not working on a very short project. You need to think ahead and plan for changes to be made in the future. If you have people who know only one particular class, you tend to be inaccessible at the moment when you like them the most (for example, sick, on vacation, etc.), and your other team members will not be able to help, because they do not know their code.
The use of precedents is based on working better, and it really helps get people to do peer code reviews in order to cross them with each other.
source
share