2 ms·
The organization of your code should not necessarily reflect the organization of your team. Well-organized code does help your team scale, but beyond that, you
by JoshTriplett 11y ago
The organization of your code should not necessarily reflect the organization of your team. Well-organized code does help your team scale, but beyond that, you shouldn't have a three-pass compiler just because three teams wrote the code, and you shouldn't have object-oriented responsibility align with team responsibility; that can get adversarial very quickly.
Have a good continuous integration (CI) system. Enforce that commits must not break the build. Have good commit messages. Have a culture of code review; no line of code should go in without someone other than the author reading it. Make sure that the culture of your company or team encourages people to review code carefully; someone who finds lots of issues (real issues) should be rewarded for a keen eye, not penalized for slowing down development.
Beyond that, if your codebase is sufficiently large than no one person could ever have all of the design in their head at once, then encourage people to become experts in diverse areas: "oh, for that subsystem you should ask Adela, she knows it inside-out". Everyone should have some areas they're an expert in, and more importantly, every area should have at least a couple of experts.