Distributed.

• Ben Grohbiel on scaling remote teams, leadership, and engineering rituals

  How do feedback loops shape high-performing engineering teams?In this episode of the Distributed podcast, host Jack Hannah talks with Ben Grohbiel, Staff Engineer at Snyk, about the interplay between leadership, technical excellence, and collaboration in remote teams. Ben shares his journey from running a web dev shop to leading platform teams and eventually transitioning from engineering management back to an individual contributor role.Ben also discusses the habits and rituals that help teams stay aligned, the importance of feedback loops in decision-making, and how structuring remote teams for success requires more than just good tooling—it’s about fostering the right culture.Highlights:Transitioning from engineering manager to staff engineer: what changed and whyThe role of SpeedBacks and pairing in driving continuous team improvementHow Snyk structures its remote teams for collaboration and efficiencyThe debate around remote vs. hybrid vs. in-person setups—and what really mattersNavigating autonomy and accountability in startups vs. scale-upsIn this episode, we cover:(00:00) – Kicking things off with Ben Grohbiel(03:39) – Transition from engineering management to staff engineer(04:27) – Challenges of managing a large remote team(07:10) – The importance of feedback loops in high-performing teams(10:40) – "Speedbacks": A unique approach to rapid peer feedback(14:09) – Effective communication between teams through pairing(17:17) – A startup experience where everything clicked(23:00) – The very first team experience on Snyk(27:09) – The debate around remote, hybrid, and in-office work(30:18) – Driving effective information flow in remote teams(34:14) – The future of remote work: Unanswered questionWhere to connect further:Connect with Ben Grohbiel on LinkedIn and check out SnykFollow TupleWant to hear more? Check out distributed.fmConnect with Jack Hannah

  --------  

  36:11
• How Staff Engineers approach leading remote teams with Cassia Scheffer from Wealthsimple

  What’s the right way to operate as a hybrid team in today’s engineering landscape? In this episode of the Distributed podcast, Jack Hannah speaks with Cassia Scheffer, Staff Software Engineer at Wealthsimple, to explore her best practices for mentoring and collaborating in a remote-first environment. Cassia shares insights on balancing hybrid work cultures, the power of pair programming, and how distributed ownership empowers engineers to make better decisions. She also reflects on the challenges of feeling disconnected in hybrid setups and how Wealthsimple prioritizes customer-focused values to align teams.Highlights:The importance of balancing hybrid work cultures to foster a sense of belongingHow schema validation enables distributed ownership and better decision-makingWhy mentoring and pair programming improve collaboration and learningStrategies for driving alignment through clear documentationThe role of curiosity in planning, problem-solving, and building strong teamsIn this episode, we cover:(00:00) – Kicking Things Off With Cassia Scheffer(00:45) – Wealthsimple’s Hybrid Model and Remote-First Approach(02:38) – Why Pair Programming is Essential for Remote Engineering(04:56) – How Wealthsimple’s 400-Person Engineering Team Stays Aligned(06:58) – Scaling Communication: From Growing Pains to Real-Time Decision Making(10:18) – A Leadership Crisis and the Culture Clash That Followed(13:48) – How Hybrid Work Creates Visibility and Belonging Challenges(19:00) – API Platform Engineering: Driving Adoption Across 30 Teams(30:42) – Coaching Engineers: Pairing as a Tool for Growth and Problem-Solving(38:52) – Final Takeaway: Curiosity as the Key to Effective CollaborationReferenced:Organizational Culture and Leadership by Edgar H. Schein: https://www.amazon.com/Organizational-Leadership-Jossey-Bass-Business-Management/dp/1119212049Where to connect further:Connect with Cassia Scheffer on LinkedInMore about Cassia on her websiteMore about WealthsimpleFollow TupleWant to hear more? Check out distributed.fmConnect with Jack Hannah

  --------  

  39:49
• Dave Farley on remote work, AI, and the future of software engineering

  How does human connection shape the way we build software?In this episode of the Distributed podcast, host Jack Hannah talks with Dave Farley, renowned software engineer, author, and expert in modern software development. Dave shares insights from his 40-year career, covering everything from extreme programming to the role of AI in software engineering. He explains why pair programming is one of the most underrated practices and how fostering trust in remote teams leads to better collaboration and creativity.Dave also explores the trade-offs of remote and hybrid work, the importance of high-quality engineering practices, and why continuous delivery remains essential for building world-class software.Highlights:Why software development is a team game and not a solo endeavorHow pair programming boosts productivity and code qualityLessons from ThoughtWorks on scaling extreme programming with large teamsThe evolving impact of AI on software engineering How remote teams can not only build trust but maintain itIn this episode, we cover:(00:00) – Kicking Things Off with Dave Farley(01:33) – Dave Farley’s Path From Early Computing to Today(05:42) – Leading a Distributed Team: First Remote Experience(07:58) – Solving Remote Work Challenges Through Human Connection(11:46) – Building Trust: The Key to Strong Software Teams(15:55) – Pair Programming: The Secret to Better Collaboration(18:55) – Overcoming Resistance to Pair Programming in Teams(28:35) – How AI Is Changing Software Development Forever(36:29) – Test-Driven Development as the Future of AI Coding(40:06) – The Biggest Challenge of Remote Work: New Teams(43:14) – Finding the Right Balance Between Remote and OfficeWhere to connect further:Connect with Dave Farley on LinkedIn and his websiteFollow TupleWant to hear more? Check out distributed.fmConnect with Jack Hannah

  --------  

  44:59
• Valentina Servile, Lead Software Developer at Thoughtworks, on how to win remote work as an engineer

  How do you foster collaboration and trust in distributed engineering teams? In this episode of the Distributed podcast, Jack Hannah talks with Valentina Servile, Lead Software Developer at Thoughtworks and author of Continuous Deployment. Valentina shares how her teams leverage practices like pair programming, collective code ownership, and streamlined processes to succeed in a remote-first world.They also discuss managing cognitive load, communicating effectively across time zones, and her strategies for replacing outdated practices like pull requests with more dynamic approaches.Highlights:Why pair programming improves team dynamics and code qualityThe role of trust and alignment in distributed teamsAutomating quality gates for faster, safer workflowsHow to foster collective code ownership in remote teamsIn this episode, we cover:(00:00) – Kicking Things Off with Valentina Servile(01:59) – The Realities of Remote Work at Thoughtworks(02:13) – How Kickoffs Build Trust and Clarity in Remote Teams(04:22) – Structuring In-Person Meetings for Maximum Impact(08:20) – Effective Communication Between Distributed Teams(12:00) – A Cautionary Tale: When Remote Work Fails(16:02) – Pair Programming as a Management and Productivity Tool(21:55) – Why Collective Code Ownership Improves Team Performance(26:13) – Rethinking PR Reviews: Avoiding Bottlenecks in Remote Development(38:41) – The Struggle to Disconnect: Managing Notifications and OverloadReferenced:Lean Inception by Paulo Caroli: https://caroli.org/en/livro/lean-inception-how-to-align-people-and-build-the-right-product/Where to connect further:Connect with Valentina on LinkedInCheck out Valentina’s book, Continuous DeploymentEmail Valentina at [email protected] More about ThoughtworksFollow TupleWant to hear more? Check out distributed.fmConnect with Jack Hannah

  --------  

  40:07
• Kent Beck on why software development is an exercise in human relationships

  How do relationships shape success in software development?In this episode of the Distributed podcast, host Jack Hannah talks with Kent Beck, renowned software engineer and signer of the Agile Manifesto, to explore how fostering relationships and psychological safety drives long-term success. Kent shares lessons from his career, including insights from Facebook and Gusto, emphasizing the role of empathy and collaboration in building sustainable practices.Kent also shares his perspective on strengthening team connections, building effective routines for remote work, and balancing productivity with well-being to help teams thrive.Highlights:Building psychological safety by addressing relationship challenges and fostering trustKent’s experiences at Facebook and Gusto: lessons on balancing technical ambition with human connectionEstablishing team rituals like daily and weekly check-ins to strengthen cohesion in remote settingsThe impact of creating an environment where collaboration and empathy drive better outcomesExploring how relationships and thoughtful communication shape software development practicesIn this episode, we cover:((00:00) – Kicking Things Off with Kent Beck(00:54) – Helping Geeks Feel Safe: Kent’s Mission and Perspective(05:51) – Software Design as Human Relationships: The Tidy First Approach(09:43) – Lessons from Facebook: Managing Relationships and Overcoming Resistance(13:58) – Building Credibility Through Contribution and Apprenticeship(19:01) – Remote Work Rituals: Fostering Connection and Collaboration(25:49) – Balancing Productivity with Teaching: Strategies for Distributed Teams(30:25) – Mentorship in Remote Work: The Value of Generational Knowledge(37:30) – The Forest vs. The Desert: How Environments Shape Creativity and Output(48:25) – Creative Leverage: Big Wins Through Collaboration and VisionWhere to connect further:Connect with Kent Beck on LinkedIn and his WebsiteFollow TupleWant to hear more? Check out distributed.fmConnect with Jack Hannah

  --------  

  50:05

Więcej Technologia podcastów

Trendy w podcaście Technologia

O Distributed.