@twobirds/microcomponents/public/documentation/why.md

Micro Components Organization Class

## Why would I give this a try?

It is lightweight, proven and can yield positive results immediatly.


### **As the CTO**:

- **Reusability**: this works with every Javascript framework that allows for DOM access, and it will work as long as the DOM exists in browsers. That is, forever.
- **Scalability**: scales perfectly by design.
- **Interoperability**: where many teams in different projects should share specific business or UI logic, you want to have something that works in any JS framework you use.

### **As a Project Manager**:

- **Separation of Concerns**: since this is a modular approach you can **split UI logic from Business logic** and let diffent teams work on each.
- using this, you can **work with external developers without the need to give them access to your projects code repository**.
- you will find out that this allows your project to **become independent from the "tools hell"**. You tend to use **DIY** modules where you had tools before.

### **As a Javascript Developer**:

- The learning curve to use this is more than shallow. 1 hour should be enough.
- This is based on **plain Javascript/Typescript, HTML and CSS**. There is no abstraction layer.
- From the very start **it is fun to work with**. You are back in control of your code without bigger frameworks, but you are able to interact with them.
- You can **work for any customer right away**. **No training on their system required**, just fulfill their micro component requirements.
- Over time, you can **build your own framework or functional libraries** from scratch.