Inclusive Architecture - Building a Sustainable Dev Team
summary
Claims that an explicit Pam stack — Process, Abstractions, Mentorship makes teams cheaper and faster: concrete steps include writing plans and checklists, using CLIs (Ember/Angular) and frameworks (AMP image) to reduce hand‑rolled work, adopting TypeScript and state machines (xstate, Ryan Florence’s checkout machine) to isolate complexity, and running formal mentorship (Sun found mentees are 5× more likely to be promoted). Examples: a client spent a week rewriting a router instead of using a standard one; state machines and design systems (Shopify Polaris, Material) demonstrably lower maintenance.
AI-written summary · about
chapters (20)
- 0:00Start
- 3:31How non-inclusive projects hurt juniors
- 4:52How non-inclusivity actually hurts everyone
- 9:25THE BENEFITS OF PROCESS DONE RIGHT
- 11:24HOW TO CREATE PLANS
- 15:49EFFECTS OF REVIEWS
- 17:57REVIEW, REVISE, ITERATE
- 19:03WEB DEVELOPMENT IS HARD
- 19:37WEB DEVELOPMENT 101
- 21:194 AMP
- 22:10ANGULAR CLI
- 23:39STATE MANAGEMENT
- 25:10TYPESCRIPT
- 26:58DESIGN AND USER EXPERIENCE
- 27:44DESIGN SYSTEMS
- 28:34COMPONENT LIBRARIES
- 29:18STATE MACHINES
- 32:03WHAT'S IN IT FOR MENTEES
- 33:19WHAT'S IN IT FOR OTHERS
- 38:35HOW JUNIORS CAN HELP THEIR
related talks
29mCreating a better culture in tech through D&I
43mScalable Best Practices for Your Development Team
29mIntentional Architecture in Agile Organizations
33mBuilding resilient frontend architecture
50mCoevolution of Architecture & Code - Closing The Gap
40mBuilding resilient frontend architecture
40mPractices from trenches for embracing evolutionary architecture in wild
46mAdaptive Socio-Technical Systems with Architecture for Flow