Making what you have enough
summary
A fintech customer-facing service hits capacity, takes 10 hours to restore, and forces an 18‑month deadline to rearchitect from a rigid server stack to a flexible one; the team measures CPU and memory, finds spare hosts, prioritizes via an arc (largest item first), funnels work through one intake, uses feature flags and smaller gated releases, runs weekly risk reviews, drops nonessential work like a new marketing site, and after migration sees higher than expected traffic within six hours — the rebuild works.
AI-written summary · about
chapters (14)
- 0:00Welcome
- 1:02Work change
- 3:30Payfair and fintech
- 4:58Scarcity and constraints
- 6:22Action over denial
- 7:24Existing resources
- 8:48Flexible server stack
- 9:29ARC framework
- 11:19Weekly reviews
- 12:23Team needs
- 13:47Release barriers
- 15:3218-month journey
- 16:15New system success
- 16:36Key takeaways
related talks
26mRebuilding at scale: A CTO’s journey in a high-growth fintech
20mHow Misjudging the Importance of an Unloved Project can Turn Into a Dis
30mProduction › Prototype: How a Small Team Replaced a Core Platform in 90 Days
38mMore Money More Problems
30mLearning from Learnings: Anatomy of Three Incidents
20mDoing Things the Hard Way
28mThe Failing CTO - What we can learn from others' mistakes
31mThe fine lines between chaos and order