diff -r 204f6466c03b -r 7a27e64cee67 text/ssm.en.xml
--- a/text/ssm.en.xml Tue Oct 08 17:21:13 2019 +0200
+++ b/text/ssm.en.xml Wed Oct 09 10:30:14 2019 +0200
@@ -264,6 +264,13 @@
e50424e8-94f3-48aa-bf01-0ba984eb2349requirementLarger and multi-purpose software must be divided into smaller modules.
+
+ http://wiki.apidesign.org/wiki/NetBeans_Runtime_Container#Modularity_Manifesto
+ compatible
+
Modularity Manifesto
+ Splitting application into modules can greatly improve the design. It is not hard to guess that a monolithic piece of code where every line in any source code can access any other source file is much more interconnected and unreadable than a code which introduces many modules and allows such uncontrolled calls to happen just inside the module.
+ Modularity would give systems clearer design, control of dependencies between modules and give developers more flexibility in maintanence. Think about it when starting any new project - nevertheless big it is, do it in modular way. It is going to be big plus for the architecture of the whole application as it grows from its child days.
+
e752efae-75c9-4620-aa14-65c4949a3609