The document discusses componentization patterns in software development including container/presentation components, composition versus inheritance, and popular patterns like smart and dumb components. It provides guidance on when to keep state in container versus presentation components and examines current trends in programming languages like JavaScript and React favoring composition over inheritance for managing component states and user interactions.

1. - A B R A A R S Y E D
COMPONENTIZATION
PATTERNS

2. Reusability
Separation of concerns
WHY COMPONENTIZATION?

3. HOW TO
COMPONENTIZE?
Container/Presentation Model
Composition vs Inheritance
POPULAR PATTERNS

4. CONTAINER PRESENTATION
Smart Components
Contains other
Container/Presentation
components
Handles REST Calls
Handles Data
Transformations
Dumb Components
Can contain only
Presentation
components
UI Centric
Handles User
Interactions

5. WHEN TO KEEP STATES IN
CONTAINER COMPONENT?
HANDLING
USER
INTERACTIONS
WHEN TO KEEP STATES IN
PRESENTATION COMPONENT?

6. SUMMARY
Reusability
Separation of concerns
Higher Order Components
State Management Solutions

7. CURRENT TRENDS IN
PROGRAMMING
COMPOSITION VS INHERITANCE
WHAT DOES JAVASCRIPT SAY?
WHAT DOES REACT SAY?

8. QUESTIONS ANSWERS AND

9. THANK YOU :)
Twitter: @iamabraarsyed
Mail: abraar@jnaapti.com