More Money More Problems
summary
Teams hit four recurring technical inflection points as growth brings more customers and more problems: legacy systems require rewrites and designers should build for deprecation so migrations stay incremental; stop inventing every commodity and play to core strengths or buy expertise; accept failures will happen and invest in detection plus automated mitigation like “red buttons”; and measure developer experience — aim for 2x with half the people by automating toil and track simple metrics (for 100 people keep ≤3 metrics, split work ~50–60% features, 15–25% ops, 10–20% investing).
AI-written summary · about
chapters (11)
- 0:00Introduction
- 2:09More money more problems
- 4:41Team/company growth phases
- 9:13Technical challenges
- 9:55Systems needing rewrites
- 14:29Core strengths and leverage
- 19:26Preparing for bad things
- 24:01Scaling with automation
- 25:29Developer experience
- 28:43Key takeaways
- 37:37Q&A
related talks
20mDoing Things the Hard Way
39mStop Focusing on Tech Debt
29mNavigating the chaos of scaling
07mManaging in hard times: How to shift from growth to stability
24mFrom Startup to Scale Up Designing for Growth from Day One
31mBalancing New Features While Maintaining Quality
47mContinuous Deprovement will eat your product for breakfast
31mManaging Growing Pains: Thinking Big While Being Small