Scalable Best Practices for Your Development Team
summary
A team composes five or six standalone apps into one product, uses readme-driven development to lock APIs, creates operational-ui (a React UI library), starts with glamorous then writes a codemod with Babel to migrate 100+ components to emotion, publishes operational-scripts like create-react-app, automates recurring work with Hygen/plop, layers a data-fetch abstraction, plans Apollo/GraphQL migration while currently using REST, and exposes a hidden devmode to capture reproducible bug reports.
AI-written summary · about
chapters (29)
- 0:00Introduction
- 1:02About Tejas
- 1:24ConTiamo
- 3:03Topic
- 5:12Complexity
- 6:55Mental Health
- 7:48Your Brain Doesnt Have a Fix
- 8:19Does Your Solution Work
- 9:23Essentials
- 10:31Testing
- 11:37Write tests
- 14:41Test
- 15:00Technical Debt
- 16:35Solutions
- 17:15RDD
- 19:00Operational UI
- 21:09Take the time
- 22:48Onetime vs recurring
- 23:21Use cases
- 28:48Divide and Conquer
- 30:17Fill the gaps
- 32:12Cloud team
- 35:06Basic
- 38:58Accessibility
- 41:22Feedback
- 42:36Nielsen Study
- 43:20Recap
- 43:45Final point
- 44:26QA
related talks
43mScalable Best Practices for Your Development Team
35mThe Great Modularization: How We Scaled a 15-Team React Native App Without Losing
24mManage Your Huge Codebase like a Boss
15mApplying Microservices Design Patterns to Scale React App Development
32mYour Guide to Making Scalable Design Systems
28mBack to React: The Story of Two Apps
46mBuilding Reusable Components ... That Are Actually Reusable
43mRethinking SPAs: web-native apps