Modularizing Your Application
Defining clear ownership boundaries minimizes conflict between developers and teams, but it will not help to reduce the energy required to understand the application or even a piece of it. An onboarding engineer getting into an application with millions of lines of code will not be reading them all. Most probably, the newcomer will not be checking the CODEOWNERS file to read all the files owned by the team. Moreover, there are other problems related to having a large monolithic codebase. This kind of codebase typically lacks a clear structure, becoming the infamous “Big Ball of Mud.” In a 1997 paper aptly titled “Big Ball of Mud,”[116] the authors, Brian Foote and Joseph Yoder, explore what they call “the most frequently ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access