2026-06-19 –, E105 (capacity 70)
You don’t jump 1,197 spots on the PyTorch contributor leaderboard by accident. As an Agile Practitioner, I wasn’t the one writing the commits—I was building the highway so they could actually merge. This talk pulls back the curtain on the unglamorous but powerful processes that helped scale our open-source impact. I’ll share how we streamlined community contributions, removed friction for external developers, and evolved our internal Agile practices to move at the speed of the broader PyTorch ecosystem. If you want to amplify your team’s open-source impact, you’ll see why the right workflow isn’t just helpful—it’s a competitive advantage.
Saiesh began in engineering, solving technical problems before bravely deciding people were the real puzzle. He became an agile practitioner, swapping DSA for delivery metrics and learning that debugging humans is far less predictable than debugging code. Today, he engineers high-performing teams with precision (just fewer hard hats and more sticky notes). When he’s not coaching teams, he’s probably reminding someone that “it depends” is, in fact, a complete answer.