Skip to content

Commit

Permalink
Update README.md
Browse files Browse the repository at this point in the history
  • Loading branch information
tom-sapletta-com authored Nov 10, 2023
1 parent a7febd3 commit c4ddd6c
Showing 1 changed file with 28 additions and 24 deletions.
52 changes: 28 additions & 24 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -34,34 +34,22 @@ From #clean ideas to code #smells ... Let's talk about The Pragmatic Development
development = production of **code** to implement **services** based on **requirements**


## Modular principles

![hypermodularity](https://github.com/tom-sapletta-com/modular-code/assets/5669657/87475ed6-5a5e-432a-a6e2-8174952f14d7)



### Environment
+ **management** over production
+ **requirements** over expectations

### Source-code
+ **reusability** over code development
+ **writing** over refactoring code
## Modular code of network

### Data
+ data **standardization** first
+ **fat-data** over fat-function
![Modular code of network](https://github.com/coders-info/www/assets/5669657/ccee5072-87d6-413c-ba33-37d4777d8a8f)

In modular code of network, modular principles help by encouraging the development of concise, focused, and reusable modules that interact with well-defined interfaces, making the overall system robust and adaptable to changes.
Using these principles, developers are encouraged to pay attention to the bigger picture, strive to maintain consistency in code structure, and promote maintainability and scalability.

Hypermodularity refers to an advanced or extreme degree of modularity in the design and organization of systems, products, technologies, or processes. Modularity itself is a design principle of creating complex systems from smaller, easily managed, interchangeable and often standardized parts or modules. The concept of hypermodularity has been taken to the next level, where modularity is extremely pronounced, allowing for even greater flexibility, customization, interchangeability and scalability.

## Modular code of network


![modular-code-of-network](https://github.com/coders-info/www/assets/5669657/e9588bea-6c16-455f-a829-609b6390abbd)
This mind map starts with the central concept of Modular Code Networks and branches out into three main subtopics:


### Core Principles
### Modular Principles
It emphasizes the key attributes of modules in a modular code network, including being concise, focused, reusable, and having well-defined interfaces that enhance robustness and adaptability.

### Expected Outcomes
Expand All @@ -71,12 +59,6 @@ By following the modular design principles, developers should aim for the larger
Lastly, it elaborates on the concept of hypermodularity as an advanced form of modularity that offers even greater degrees of flexibility, customization, interchangeability, and scalability.


In modular code of network, modular principles help by encouraging the development of concise, focused, and reusable modules that interact with well-defined interfaces, making the overall system robust and adaptable to changes.
Using these principles, developers are encouraged to pay attention to the bigger picture, strive to maintain consistency in code structure, and promote maintainability and scalability.

Hypermodularity refers to an advanced or extreme degree of modularity in the design and organization of systems, products, technologies, or processes. Modularity itself is a design principle of creating complex systems from smaller, easily managed, interchangeable and often standardized parts or modules. The concept of hypermodularity has been taken to the next level, where modularity is extremely pronounced, allowing for even greater flexibility, customization, interchangeability and scalability.




## Hypermodularity
Expand All @@ -94,6 +76,28 @@ This is the hyper modular network of code ...



## Modular principles

![hypermodularity](https://github.com/tom-sapletta-com/modular-code/assets/5669657/87475ed6-5a5e-432a-a6e2-8174952f14d7)



### Environment
+ **management** over production
+ **requirements** over expectations

### Source-code
+ **reusability** over code development
+ **writing** over refactoring code

### Data
+ data **standardization** first
+ **fat-data** over fat-function





## Why and How?

Modular programming is a software design approach that focuses on breaking down programs into independent, interchangeable modules where each contains everything necessary to execute a specific functionality. This separation simplifies complex systems, makes the code easier to manage, and promotes code reuse. Here’s how each of the principles you've mentioned fits into modular programming:
Expand Down

0 comments on commit c4ddd6c

Please sign in to comment.