Scalable Best Practices for Your Development Team
summary
Lists concrete changes and results: adopt Readme-driven development so component APIs exist before code; build an open Operational UI and scaffold via operational scripts to remove per-project tooling; prefer integration-heavy testing with static analysis (TypeScript) and the testing trophy; replace Redux by Hydrogen for boilerplate reduction; run a Babel codemod to convert Glamorous to Emotion and upgrade 100+ components in minutes; automate recurring tasks, split roles (styling, SSR, D3), and measure improvements in velocity and maintainability.
AI-written summary · about
chapters (30)
- 0:00Introduction
- 2:20Scalable Best Practices
- 4:28Complexity
- 7:32Scale
- 7:46Team
- 8:29Deferred Essentials
- 9:57Testing
- 11:33Write tests
- 11:57Pyramid of tests
- 13:38Testing trophy
- 15:03Testing JavaScript
- 15:28Technical Debt
- 17:29Not a Silver Bullet
- 18:15BehaviorDriven Development
- 20:08UI Component Library
- 22:25Take the time
- 24:15The 0 1 N principle
- 25:12Hydrogen
- 30:57Divide Conquer
- 32:20Dividing by Function
- 34:20Cold Site
- 34:35Embrace Structure
- 34:46Define Structure
- 37:08Embracing Structure
- 37:23To Dos
- 39:47Accessibility
- 40:55Feedback
- 41:32Feedback Statistics
- 41:51Evolution
- 42:10Communication
related talks
49mScalable Best Practices for Your Development Team
25mDefault to Consistent
28mSome small steps for code, One giant leap for quality
45mPaving the adoption path of your Design System for engineers
28mLessons in Managing Technical Debt
40mRefactoring large JavaScript codebases
30mOptimizing for Developer Delight
27mScaling Your Front-End in a Realistic Way!