I work in a small company - four developers working on various projects. We looked at what we can do as cost-effective methods to improve the process, and an idea came up.
Given what we do, we often have individual developers working on parts of the system, independent of other developers. This can have a number of negative consequences:
- The developer may not be fully aware of the context in which the change is made, and make changes in a way that will meet the current needs of the client, but will disrupt the functionality that other clients depend on.
- The developer can make changes that violate the current architectural design by introducing a dependency that will cause problems in future development.
- Other developers may not be aware of how the system has changed in areas where they did not work.
We talked about code reviews as a way to solve these problems. But we did not have much success when we tried. It takes a long time to prepare the changes for reviewing the code, and this leads to the fact that everyone does not work while checking is performed. And the benefits of any review we tried were minimal.
We use Subversion (with TortioseSVN) as our VCS. I looked at the SubVersion CommitMonitor tool and wondered if it could work as a kind of code review for minors. It lists all the commits made in the repository, allowing anyone to see the changes made, the log messages made for this change, the files that were included in the change, and the specific lines in each file that were changed.
, , , , , , . , , .
- , , , , , , , , .
- - , ?