Architecture for Cross-Functional Teams
summary
Talk examines software architecture for cross-functional teams working in a shared codebase, addressing coordination problems like avoiding interference, finding senior analysts, and preventing “tragedy of the commons.” It compares architectural approaches across backend and mobile (iOS) and uses a cascade of metaphors—drawn from formal logic, relativity, and quantum field ideas—to give memorable guidelines for evolving architecture as a company grows.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:29Modern architecture problem
- 2:30Three architecture principles
- 6:03Car-sharing practical example
- 7:29Evolution to superapps and cross-functional teams
- 13:56Overloaded concepts problem
- 15:43Physics as architecture foundation
- 18:08Imperative vs functional state
- 23:23Scenario as wave independence
- 29:44State rejection and time quantization
- 31:51Parallelization and artifact exchange
- 34:17Cross-functional teams as sources
- 37:29UI visualization and work
- 41:40Fractality and business resonance
- 43:24Conclusion
related talks
44mWhen your boss decides to have an architecture team…
31mHow and Why to Design Your Teams for Modern Software Systems
35mOrganization: A Tool for Software Architects
46mTHE too MANY FACES OF ARCHITECTURE
41mSoftware architecture as a contributor to high performing teams
51mSoftware Architecture for Humans!
43mSoftware Architecture, Design Thinking & Knowledge Flow
45mTeam and Software: Making an Impact as an Architect