Lightning Talk: The Immense Benefits of Not Thinking in Screens
summary
Codebases rot because teams map entire screens to single modules, which creates deep coupling and makes reuse painful. Replacing screen-sized pieces with a tree of small, black‑box nodes yields self‑documenting interfaces, natural DI scopes, simpler instrumentation tests, and reduces extraction time from two weeks to minutes. Implementation uses a fork of Uber RIBs that adds state restore and backstack routing, is already in production, and proves the node tree approach actually works.
AI-written summary · about
chapters (10)
- 0:00Introduction and problem
- 2:28Symptom of coupled mess
- 4:12Root cause of coupling
- 5:55Modular architecture approach
- 7:18Self-documenting module design
- 9:06Universal abstraction from screens
- 10:11Hierarchical module structure
- 11:58Decoupling and reusability benefits
- 12:40Secondary advantages of approach
- 13:43Library implementation and demo
related talks
27mLightning talks - frontend
58mIntentional Code - Minimalism in a World of Dogmatic Design
34mFunctional UIs and Unidirectional Dataflow
56mThe Web, Its Frameworks and Its Standards: Deconstruct to (Re?)Construct
34mMicro Frontends
41mUsing Boundary-Driven Development to beat code complexity
26mClear Architecture in the small
35mAvoiding code spaghetti by making ravioli