4 ms·
The best way to deal with the problem is still tried and true modularization. Also it helps to merge/deploy frequently. If you have multiple people editing sa
by lmilcin 5y ago
The best way to deal with the problem is still tried and true modularization.
Also it helps to merge/deploy frequently.
If you have multiple people editing same code it is bound to cause some problems. The best way is to not have multiple people editing same code by separating them either by bounds of time or by APIs (can be separate packages, modules of the same application).
- rgoulter 5y agohttps://en.wikipedia.org/wiki/Conway%27s_law https://en.wikipedia.org/wiki/Conway%27s_law If by APIs or module boundaries, then this smells like Conway's Law: the organization of code mirrors the organization of people.
- lmilcin 5y agoIt is true and it actually aids modularization. Teams have natural tendency to produce separate modules from other teams so that they can manage their development process more effectively. Then you can consider individual team members working on their own modules. In this case the modules also can be a reflection on how the task was delegated to the team because how you split the task between multiple team members may end up how the boundaries between modules were designed. But it does not necessarily have to be this way. Design decisions should be made consciously and selecting how to break up your application into modules is an important design decision.