How we drive Developer Productivity at Yelp
summary
Engineered a decade of developer productivity at Yelp: moved from a monolith with millions of Python lines and 100,000 tests (running two days sequentially) and 40‑minute clean builds to a SOA of ~400 backend and ~40 front-end services. Built tools and processes: pre-commit, a custom Docker compose replacement, a developer playground, dependency tool Yokyo Drift, and the Gondola web platform plus GraphQL and ownership via YAML. Metrics arrive in 2017; paved‑path adoption rises and LLMs are piloted for code mods.
AI-written summary · about
chapters (8)
- 0:00Introduction and Background
- 3:13How it started
- 6:29Yelp’s EE Journey: Part 1 – The Monolith Problem
- 11:00Yelps EE Journey: Part 2 – SOA
- 19:52Yelp’s EE Journey: Part 3 – Best Practice
- 22:00Yelp’s EE Journey: Part 4 – Current State
- 24:00Upcoming challenges and opportunities
- 25:30Q&A Session
related talks
39mMobile Developer Productivity Panel
42mBuilding DevX Teams, my story
28mRefactoring Your Team For Fun and Profit
45mFrom 5 to 100 in Product Development team in just 5 years
48mMobile Developer Productivity at Scale
19mReducing Context Switching & Unplanned Work Through Platform Engineering
52mSurviving the Techpocalypse with Developer Productivity Engineering
29mHacking Development Culture: Treating Developers As People