Distributed.

Jack Hannah, Tuple
Distributed.

Remote work is here to stay. Whether you’re firmly in the return to office camp or die hard distributed, the cat’s out of the bag for the industry. The Distributed podcast, from Tuple, deconstructs how world-class engineers and their teams navigate the challenges (and opportunities) remote work creates. Host Jack Hannah uncovers stories of teams and individuals overcoming technical challenges, working through interpersonal dynamics, and battling their own distractions. Through these conversations, we’ll unpack the practical side of how folks work together in this new normal, and dig into the social emotional piece so often overlooked in programming.

  1. 1天前

    Inside the 3rd largest Rails monolith in the world with Cisco Tech Lead Ed Gibbs

    How do you drive change in large engineering teams? In this episode of the Distributed podcast, host Jack Hannah talks with Ed Gibbs, Software Engineering Tech Lead at Cisco Meraki, about his journey from physics to software engineering and how he’s championed better development practices over the years. Ed shares insights on navigating remote work, driving incremental adoption of engineering improvements, and fostering collaboration in large-scale teams. Ed also discusses the role of experimentation in engineering culture, the benefits of meandering syncs over traditional standups, and the challenges of balancing refactoring with delivery in a complex codebase. Highlights: Why Ed Gibbs wears a fez every Friday and how it helps him succeedLessons from scaling change across 1,000+ dev organizationsThe engineering rituals that help his teams excel, like meandering syncs and mobbing Mondays In this episode, we cover: (00:00) – Kicking things off with Ed Gibbs (01:03) – The origin story of Fez Friday and making remote work memorable (07:04) – Inside Ed’s fully remote team setup at Cisco Meraki (09:26) – The early days of TDD and what made it stick (12:04) – Introducing CI and getting buy-in for testing (17:16) – How to drive consensus across a 1000-engineer company (23:46) – Team habits Ed is proud of, from Kanban to mobbing Mondays (30:06) – What meandering syncs are and how they work References: Blog post on meandering syncs: Stand-Up Meetings Are Dead (and What to Do Instead) Where to connect further: Connect with Ed Gibbs on LinkedIn and his website Follow Tuple Want to hear more? Check out distributed.fm Connect with Jack Hannah

    41 分钟
  2. 6月26日

    Principal Engineer at Salesforce on collaborative programming with James Simone

    On this episode of the Distributed podcast, host Jack Hannah talks with James Simone, Principal Engineer at Salesforce, about how he went from no development experience to principal engineer in 7 years at a Fortune 500 and the effects of collaborative programming.  James shares what things are like inside the agile org at Salesforce and how they approach remote work, including how they prioritize reflection and team agreements to foster productive and happy work environments. Highlights: James's journey to principal engineer The role of reflection in boosting productivity and happinessSalesforce's approach to ensemble and pair programming  In this episode, we cover: (00:00) – Kicking things off with James Simone (01:09) – The empowerment of distributed teams: fostering community and learning (03:08) – Inside Salesforce's agile organization: a structural overview (04:17) – Legacy projects and measuring developer happiness (06:07) – Applying metrics: individual and executive perspectives (08:52) – Collaborative programming: a measured approach (11:03) – Starting the week: Monday morning routines (12:56) – Code review: transitioning from author to reviewer (14:26) – The role of working agreements in team dynamics (17:05) – Reflection and improvement: the impact of test-driven development (22:36) – Documentation and decision-making in collaborative teams (27:48) – Balancing career growth with personal life passions References Test Driven Development: By Example by Kent Beck Domain Modeling Made Function by Scott Wlaschin Where to connect further: Connect with James Simone on LinkedIn and on his website Follow Tuple Want to hear more? Check out distributed.fm Connect with Jack Hannah

    31 分钟
  3. 6月19日

    6x founder and Shopify Principal Engineer on AI, Rails, and pairing with Obie Fernandez

    In this episode of the Distributed podcast, host Jack Hannah sits down with Obie Fernandez, Principal Engineer at Shopify, 6x founder (including Andela and Hashrocket), and prolific author and musician. Obie reflects on his early role in the Ruby and Rails communities, what led him to shift away from Java, and how he uses and thinks about AI. Obie goes deep on how he and his team at Shopify uses AI, while touching on what this means for pair programming, mentorship, and the future of software development. Highlights: How Obie made Rails mainstream at ThoughtWorks and beyondHow Obie and Shopify use AIReflections on pair programming and the future of software development In this episode, we cover: (00:00) – Opening the conversation with Obie Fernandez (01:59) – What made Ruby stand out after years of Java (07:45) – Driving Rails’ adoption at ThoughtWorks and shaking up the status quo (15:54) – How Shopify thinks about the developer experience (20:19) – Why every developer should experience pair programming (25:03) – How Obie uses AI (27:15) – The future of software development and collaboration (33:13) – When to stop vibe coding and prioritize quality (34:04) – Big P vs little p pair programming References: Patterns of Application Development Using AI Shopify CEO Tobi Lutke's now infamous AI memo Where to connect further: Connect with Obie Fernandez on Instagram and obiefernandez.com Follow Tuple Want to hear more? Check out distributed.fm Connect with Jack Hannah

    39 分钟
  4. 6月5日

    Agile Otter on why most devs work in the worst ways possible

    How does the future hold for software development with remote collaboration? In this episode of the Distributed podcast, host Jack Hannah chats with Tim Ottinger, aka the Agile Otter, about how to manage and organize the work. Among other things, Tim is a Senior Consultant at Industrial Logic, contributor to the book Clean Code, and active presence online. Jack and Tim explore various ways to work in teams instead of solo and the various benefits they offer. Highlights: Rethinking solo work to boost first-time through rates and productivity Tim’s experiences with Extreme Programming and Agile Introducing swarm boards  for better remote teamwork  In this episode, we cover: (00:00) – Introduction to Tim Ottinger, Agile Otter (01:11) – Tim’s background and contributions to clean code and agile (01:46) – Early remote work and why covid changed remote training (04:03) – Benefits of spreading training over weeks vs. intense sessions (06:18) – What’s wrong with how most software teams manage work today (10:42) – The problems with solo work, parallelism, and utilization myths (14:14) – How AI can help coding but still has limitations (18:07) – Why increasing first time through rate is the key metric (24:18) – How to structure teams to avoid queues and handoffs with swarm boards (30:50) – Starting with small experiments to work together and improve flow (33:12) – Don’t lower the standards of the pipeline, raise the abilities of the team (40:07) – When it comes to remote work, longitude kills and latitude hurts (41:38) – Tim’s advice for making the most out of remote work (44:05) – The law of the 2nd floor (44:51) – Things can be better, don’t lose hope References Swarm Programming with the Swarm Board Clean Code by Robert C. Martin Where to connect further: Connect with Tim Ottinger on LinkedIn and on his website Connect with Industrial Logic Follow Tuple Want to hear more? Check out distributed.fm Connect with Jack Hannah

    47 分钟
  5. 5月29日

    Emily Bache on software quality, technical excellence, and driving change

    In this episode of Distributed, host Jack Hannah speaks with Emily Bache, a technical coach and the creator of Samman Coaching, about her work helping teams improve their development practices.  Emily shares her experiences with test-driven development and refactoring, and explains how these practices can transform both code quality and team dynamics. Highlights: The impact of test-driven development on software qualityHow to introduce new practices in a resistant environmentWhy collaborative coding, like ensemble programming, accelerates team growthThe role of leadership in creating a culture of continuous learning and quality In this episode, we cover: (00:00) – Kicking things off with Emily Bache (01:25) – First experience with extreme programming in 2000 (02:28) – Struggling to get a new team on board with XP (04:03) – Why TDD transformed Emily’s coding approach (05:22) – Becoming a full-time technical coach and YouTuber (06:48) – Defining what a technical coach actually does (07:21) – Inside a high-performing architecture team’s microservices shift (09:04) – Can siloed experts still outperform collaborative teams? (14:42) – Simple tactics to nudge your team toward better practices (20:57) – Ensemble programming explained: many minds, one keyboard (24:45) – Why refactoring skills matter in the age of AI assistants References Approval Tests and the weekly Approval Tests Ensemble ChatGPT & Copilot are NOT Refactoring Tools Where to connect further: Connect with Emily Bache on LinkedIn and Samman Technical Coaching Society Follow Tuple Want to hear more? Check out distributed.fm Connect with Jack Hannah

    31 分钟
  6. 5月22日

    Cofounder of Cucumber Ltd. on RSpec, Cucumber, and legacy systems with Matt Wynne

    In this episode of the Distributed podcast, Jack Hannah sits down with Matt Wynne, staff software engineer at Mechanical Orchard and a longtime advocate for Agile and Behavior-Driven Development (BDD). Matt shares his journey from working with legacy systems to co-founding Cucumber Ltd., offering a firsthand look at how testing, pairing, and social programming create more effective teams. Matt also discusses the challenges of modernizing outdated infrastructure, the role of ensemble programming in fostering collective code ownership, and why strong relationships are essential for high-functioning distributed teams. Highlights: The power of social programming: how pairing and ensembling improve collaboration and knowledge-sharingThe evolution of BDD and its impact on software developmentStrategies for handling legacy modernization projects with minimal disruptionWhy creating psychological safety leads to stronger remote teams and better engineering outcomesThe future of automation, AI, and the next wave of innovation In this episode, we cover: (00:00) - Kicking things off with Matt Wynne (00:13) - From COBOL to modernization: Lessons in legacy systems (05:05) - The origins of Cucumber and BDD (07:44) - Pairing, ensembling, and the power of social programming (11:38) - Extracting knowledge from aging codebases (14:07) - Building tools for faster legacy system migrations (21:01) - Creating psychological safety in engineering teams (29:19) - Selling change: How to introduce new development practices (33:02) - Remote work and the importance of human connection References Working Effectively with Legacy Code by Michael Feathers Agile Coaching by Rachel Davies and Liz Sedley Where to connect further: Connect with Matt Wynne on LinkedIn and his Website Follow Tuple Want to hear more? Check out distributed.fm Connect with Jack Hannah

    37 分钟
  7. 5月15日

    Clerk Cofounder & CEO on how to build a company that delivers incredible DX with Colin Sidoti

    In this latest episode of the Distributed podcast, host Jack Hannah interviews Colin Sidoti, Clerk Cofounder & CEO, to discuss what’s allowed them to grow so rapidly and deliver such an incredible developer experience for users. Colin reflects on how limited process fosters growth and allows his team of engineers and designers to excel. Colin also provides insight into the nontraditional ways Clerk streamlines work, including their hiring practices and unique team dynamics. Highlights: Understanding how Clerk has grown through a highly autonomous team cultureColin's insights on the importance of fluid communication in a distributed teamThe pivotal role the DX Guide plays in creating an amazing productEmpowering teams by trusting their instincts and encouraging adaptability In this episode, we cover: (00:00) – Kicking things off with Colin Sidoti (03:26) – Product development at Clerk (08:29) – Remote work dynamics: synchronizing across time zones (12:54) – Importance of fluid communication: using Tuple for efficient syncs (14:44) – The role of DX Guide: maintaining high standards in product experience (22:28) – Building a culture of customer-centric development (17:40) – Evolving product offerings: from auth to billing and beyond (25:56) – Hiring for passion: finding team members who care deeply (31:55) – Simplifying user onboarding: eliminating friction for developers (33:34) – Impact of removing friction: boosting adoption with minimal steps Where to connect further: Connect with Colin Sidoti on X and Clerk Follow Tuple Want to hear more? Check out distributed.fm Connect with Jack Hannah

    35 分钟

评分及评论

5
共 5 分
6 个评分

关于

Remote work is here to stay. Whether you’re firmly in the return to office camp or die hard distributed, the cat’s out of the bag for the industry. The Distributed podcast, from Tuple, deconstructs how world-class engineers and their teams navigate the challenges (and opportunities) remote work creates. Host Jack Hannah uncovers stories of teams and individuals overcoming technical challenges, working through interpersonal dynamics, and battling their own distractions. Through these conversations, we’ll unpack the practical side of how folks work together in this new normal, and dig into the social emotional piece so often overlooked in programming.

你可能还喜欢

若要收听包含儿童不宜内容的单集,请登录。

关注此节目的最新内容

登录或注册,以关注节目、存储单集,并获取最新更新。

选择国家或地区

非洲、中东和印度

亚太地区

欧洲

拉丁美洲和加勒比海地区

美国和加拿大