The elements of scaling
summary
Company scales from a 15–20 engineer startup through a systems rewrite from Drupal/PHP into Java services with a Ruby frontend, then cuts a four‑hour weekly storefront deploy down to deploy every day by adding automation, simpler git workflows and feature toggles. Organizational fixes include rolling out a documented career ladder, running blameless learning reviews, rebuilding trust after a “culture of fear,” and trading adversarial meetings for curiosity-driven conflict to increase autonomy and shipping velocity.
AI-written summary · about
chapters (7)
- 0:00Introduction and welcome
- 0:53Scaling systems and teams
- 10:50Speed in engineering processes
- 17:09The role of structure
- 23:29Learning from failure
- 23:50Building team relatedness
- 31:35Summary and closing
related talks
49mScaling Up!
01h 02mTools for simplified large scale systems
56mKaizen-Driven Development: Carve Your Own Path
36mIT Landscape - control vs. scaling
24mFrom Startup to Scale Up Designing for Growth from Day One
38mThe Dark Side of Scale
34mWhen scalability becomes more than a buzzword, or how to saddle an unicorn
46mDigital scale-up architectural patterns