Distributed Architectures for Distributed Teams
summary
Argues that splitting a large front end into many small apps speeds onboarding and reduces hidden dependencies, shows a meetings/profile example implemented as composable components, and demonstrates GraphQL + code generation producing typed front-end models so deprecations and broken queries surface immediately. Uses React, Flutter/Dart, Typescript-like static typing and Apollo codegen; shows adding a skills field and seeing generated types appear, and removing timezone flagging errors. The result is easier contribution and safer changes. micro front ends static typing across the full stack Apollo codegen
AI-written summary · about
chapters (20)
- 0:00Intro
- 2:48App Examples
- 3:01The Golden Phase
- 5:21Brooks Law
- 8:28Onboarding
- 10:11Advantages of small teams
- 12:18Example
- 14:35Components vs Apps
- 16:02Martin Fowler
- 16:32Dependencies
- 20:16Static vs Dynamic
- 22:05JavaScript
- 22:51GraphQL
- 25:07Static Typing
- 26:36Demo
- 27:12Profile
- 28:52Smart Component
- 29:55API Call
- 31:31Troubleshooting
- 42:53Summary
