The Climb Nobody Expected: From ~#1200 to #3 rank on the PyTorch Leaderboard
summary
A corporate engineering team details how it climbs roughly 1,197 leaderboard spots to reach the top three by changing how work happens not what is built: adopting an async‑first workflow, requiring upstream alignment before coding, enforcing a ruthless internal review and internal SLA for PR responses, and splitting features into atomic PRs. Concrete results include many PRs merging within 48 hours once maintainers co‑author the design and overall merge times shrinking from weeks to days, plus higher maintainer trust and steady contribution velocity.
AI-written summary · about
chapters (10)
- 0:00Corporate agile meets open source
- 1:05PyTorch differences
- 6:05Agile failures upstream
- 8:52Red Hat’s PyTorch shift
- 9:14Open source limits
- 11:03Embrace the asynchronous void
- 13:32Fractured team struggles
- 16:02Micro momentum focus
- 18:50Open source collaboration
- 20:19Q&A
related talks
33mWorking backwards
25mDeveloper Joy – How great teams get s%*t done
29mBreaking the PR Review Bottleneck
39mDev Team Metrics that Matter
34mScaling the Mountain: A Framework for Tackling Large-Scale Tech Debt
42m7 Metrics to Accelerate Delivery without Damaging Culture
15mDev Team Metrics that Matter
44mPanel - Graph Leadership - Scaling the Graph Across Your Org and Platform