Keeping your codebase Small and easily readable

Initially, starting a software project with only one or two source files is ideal. The code is simple to compile, run, modify, and remember where each function or class is defined.

Then, as the project expands, your directory becomes increasingly crowded with source files. You'll need many directories to organize everything. It's more difficult to remember which functions call which, therefore locating issues requires more effort.

Eventually, you'll have a large amount of source code split over multiple directories. The project is vast and no one person has a comprehensive understanding of it. Adding new features is difficult, and dealing with the code is tedious and unpleasant.

The universe follows a natural law: as a coordinated system increases, so does the complexity required to hold it together.

The best approach to cope is to maintain your codebase as compact and lightweight as possible, even as your project grows.

? Use as much general "utility" code as feasible to eliminate duplicated code.

? Eliminate unneeded code and functionalities.

? Keep your project divided among unconnected subprojects.

? In general, consider the "weight" of your codebase. Keep things light and agile.