View source for Application modularization, encapsulation, and naming for better reuse and maintenance

==Before you begin==
Modularization, if overdone can increase the code size and affect the performance of your application. You must hence consider the following key points before you choose to modularize the code: 

* The modules must be reusable. Research any present or future use cases where the module can be applied.
* Every small function in your application does not require to be a module. For example, setting up a property by copying an input parameter need not to be a module.
* If it is a small one-off application that will not be maintained or extended in the future, it may be better to avoid modularization in favor of faster implementation.
* Modularization can also be a good choice when you have a large team that must collaborate and build the application, provided that the application can be functionally and technically divided into smaller modules.