Based on my highlights
Disclaimer This chapter is a mix between my thoughts and my notes. My notes are fully based on the text, so, if you want to check exactly what the author said please refer to the highlights.
Our modules will live in a constant movement, before we mentioned about differents things to do and consider when a module grows, and a few other when its shrinks. Most of the tips and recommendations were focused on the interface of our component. After we have a clear vision and a well defined interface is good to work with the internals to increase their quality. In this case a higher quality module is directly related to how easier it is to understand its internal logic.
As I said before,
Internals of the components should be as easy as possible to understand.
When features come at a pace we cannot keep up with a simple module. We should start changing our methods and start considering reviewing the responsability of our modules consistently. Keeping your module clean at every stage is vital if you don't want to end up with entagled code.
A framework as a high level module, also hinders the complexity of probably a hard problem solved. When we opt in for a framework we don't only bring all the benefits this will bring with it. We also marry with their desitions, goods or bads. In most cases we should identify which practices we want to embrace from a framework and which others we should avoid. We can use linting rules to enforce this behaviours but also a good project structure. With clear rules at the time of implementing the different artifacts will serve as a guide to a simpler architecture.