this slides cover component driven methodology methodology and the existing problems it tries to solve. Slides considers the benefits of developing the components outside of regular app: they become more maintainable and testable, it's easier to work on them in the large team.
The main focus of the slides is about the tools and rules which helps to use CDD
9. - Duplicated functionality
- Block each other work
- Too many merge conflicts
- MR take too much time to be merged
- hard to find the place to start the task with
PROBLEMS TO
SOLVE:
36. WHY CDD?
- work in parallel
- easier to review and test
- new developers starts faster
- easier to maintain
- easier to setup css regression
testing
38. WHY NOT CDD?
- Time consuming
- treated as auxiliary project.
- seen as a tool for devs (not
business)
- it's often created after project
started
39. - One task - one component - one PR
- isolate it using component explorer
- cover all possible states at once
- code-review: ensure rules are followed!
HOW-TO
RULES