3 ms·
I don't understand how this isn't mitigated by a CODEOWNERS file[0]. Give the directories to the teams that should own them, and now they have absolute control
by mbo 4y ago
I don't understand how this isn't mitigated by a CODEOWNERS file[0]. Give the directories to the teams that should own them, and now they have absolute control over the PR review process accordingly (and responsibility of incoming code for the directories that they own too).
[0] https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners https://docs.github.com/en/repositories/managing-your-reposi...
- scarmig 4y agoThat just solves one problem, and not the most significant. Other issues, not usually inherent to the monolith pattern but very common: * Release management coupling * CI coupling * Deployment coupling * Binary bloat * Monitoring/alerting/logging noise * Lack of security policy granularity * Language and library choice coupling Of course, people mess these things up with the service model as well, but the failure modes there don't propagate as much (unless they're organizationally mandated...)