Shipping Through Chaos: Engineering Resilience Across Borders
summary
A cross-functional effort ships a C2B capability across 10 teams, 7 backend services and 3 client platforms under legal ambiguity and a reorg, coordinating across 2 timezones and multiple staging environments. Engineering work includes 61-page design doc, 30K+ backend lines changed in 2 months, API scopes for least privilege, webhooks that enable a fivefold profit uplift, duplicated eligibility checks to close week-long race windows, a one-week dev→prod approval lag, daily Slack review threads and a Russian roulette code-review automation.
AI-written summary · about
chapters (6)
- 0:00Introduction and welcome
- 2:55Project overview and product context
- 7:11Building resilient human processes
- 11:26Scope negotiation and team dynamics
- 15:26Reflections and lessons learned
- 26:23Q&A and closing remarks
related talks
17mBeyond DevOps – Holistic transformations in uncertain times
23mExtreme Ownership for Global Teams
22mScaling Culture of Resiliency in the Enterprise at Charter Communications
32mSynergy: Building Strong Engineering Teams
23mManaging diverse engineers for high-impact deliveries
26mScaling engineering organizations
26mMission Critical Mindset Building a Culture of Resilience in DevOps Teams
41mDesigning an Engineering org for SaaS & on-prem Delivery Models