Scaling Fast – Engineering Lessons From ~15 Years of Tech Startups
summary
Argues scaling requires hitting three axes at once: scale business team and tech with customer acquisition cost and lifetime value as the key numbers; organizes engineering into vertical product teams that own the mess so teams ship from idea to production without horizontal blocking; enforces short PRs measured in minutes and accepts imperfect merged code to avoid WIP rot; prefers standard, tweak-the-problem solutions, vertical modules and straightforward data models over early generic frameworks and overzealous DRY.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 1:13Scaling the business
- 4:05Scaling the team
- 11:51Scaling the tech
- 17:57Data and domain-driven architecture
- 19:03Closing
related talks
19mScaling Fast – Engineering Lessons From ~15 Years of Tech Startups
56mScaling Up!
46mDigital scale-up architectural patterns
30mEngineering in Overdrive: How to Thrive When Tech Evolution Goes Full Gas
27mScaling Your Front-End in a Realistic Way!
21mNeed for speed - Moving fast as a software engineer
07mFrom Scaling APIs to Scaling Data to Scaling Your Team
47mThe Only 2 Things needed to Scale Agile