Scaling Team Delivery Using Standardization
summary
Generators plus Bit components standardize scaffolding and configs so teams ship identical components and configs across projects. The demo uses EJS or plop-style templates, injects docs and tests wired to Testing Library, and shows sharing ESLint/Prettier/Tailwind as publishable, versioned config components that install via npm or yarn. Workspace generators create full starter projects and components (index, component, docs, tests, styles) so a one-time setup saves roughly five minutes per component per developer and versions let teams roll updates project-by-project.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 0:53Perfect teams vs. reality
- 1:39Ways to keep things standard
- 3:32Using generators
- 9:33Pros of using generators
- 10:20Making changes
- 13:22Configs for non Bit projects
- 17:31Conclusion
related talks
43mScalable Best Practices for Your Development Team
25mDefault to Consistent
01h 01mUseful Tools and Utils for JS Development
24mNX Generators or how to skip boring tasks
18mLeveraging Standardized Dev Environments for Peak Developer Velocity
32mKickstarting libraries of shared React components for multiple teams
34mTowards a simpler JavaScript ecosystem
43mStandardizing Microservice Development