Well, we as developers often talk about modules and their advantages. But how often do we talk about making modules meaningful, trustworthy, choosing best modular pattern erc. Good modular system is the basic ingredient of any Javascript framework. This talk would throw some light on the it’s importance.
Break down to take down: The title might seem vague but breaking down the project into meaningful modules is what most of us miss out on. Well, by meaningful I mean not only is it important to break down code base into individual modules but also to make those modules reusable. This session would also summarise my learnings while working on a product that relies heavily on the smooth working of a Javascript Library(which is obviously broken down into modules) and how we manage that. I would also talk about the different module patterns and when to use them. Moreover every Javascript framework depends on a good design system.
In short, this session would give a clear picture on how breaking down your codebase will help you take down a lot of problems.
I plan to cover the below mentioned points -:
- Why focus on this?
- Examples to depict how modular system helps in writing efficient program in less number of lines.
- Importance of making modules meaningful.
- Give more power to your modules by writing end-to-end and unit test cases.
- Different Modular Patterns -:
- Facade Pattern (pros & cons)
- Mediator Pattern (pros & cons)
Software Engineer at Wingify. Full stack developer with keen eye for writing elegant code. Loves contributing to open source projects, talk about JS and participating in hackathons.
https://drive.google.com/file/d/1z5-0vRzSx_vokUuA6MbHvunNZs8BEdaB/view?usp=sharing
{{ gettext('Login to leave a comment') }}
{{ gettext('Post a comment…') }}{{ errorMsg }}
{{ gettext('No comments posted yet') }}