In modular design, a software system is decomposed into a collection of modules that are relatively independent. Modules can take many forms, such as classes, subsystems, or services. In an ideal world, each module would be completely independent of the others: a developer could work in any of the modules without knowing anything about any of the other modules. In this world, the complexity of a system would be the complexity of its worst module.
In designing our life and future, we also need to think in terms of modules. We need to think in terms of different levels of our future. What do we do today, to ensire that tomorrow, so that next week, so that next year, so that ten years from now.
If we think about the above, we will be over-whelmed with existential dread at the complexity of the endeavour.
We should therefore only dedicate certain times to think at certain levels. Each week we should think about what needs to be done that week. Each day what needs to be done on the day. Each month, each year.
