Distributed.

How do you keep a massive, distributed engineering organization with 80,000 employees aligned and actually understanding one another? In this episode of Distributed, host Jack Hannah sits down with Ian Varley, Principal Architect at Salesforce, to talk about how he helps their thousands of engineers across global teams stay informed and connected.

Their conversation explores why clear communication is the backbone of great engineering, practical ways to disseminate knowledge across distributed teams, and how to use AI to make it all faster and easier. You’ll come away with tips you can use right away to break silos, build trust, and make information flow more smoothly in your own organization.

—

Where to find Ian Varley:

• LinkedIn: https://www.linkedin.com/in/ianvarley/

• Website: https://ianvarley.com/

—

Where to find Jack Hannah:  

• LinkedIn: ⁠https://www.linkedin.com/in/jack-hannah/⁠

• Website: ⁠https://tuple.app/⁠

—

Timestamps:

(00:00) Intro

(01:11) What “borg up” means and why shared understanding matters

(02:20) Practical techniques for using LLMs to communicate more clearly

(05:25) Why you can’t just ask an LLM to write for you

(06:45) How writing itself sharpens thinking and adds clarity

(08:34) The risk of “enshittification” in communication and how to avoid it

(09:38) Using LLMs as a true thought partner instead of a shortcut

(10:55) Why investing in shared understanding pays off in the long run

(16:55) Ian’s unique role at Salesforce as a knowledge sherpa

(22:02) How Ian’s role evolved to Principal Architect with a focus on mentoring and educating

(25:05) What Ian learned from blending engineering, infrastructure, and coordination on HBase

(30:34) How Ian amplifies impact by enabling others to spread knowledge

(33:30) How AI can make work easier

(35:15) Co-Intelligence and the framing of AI as “alien intelligence”

(36:56) Ian’s process for title generating with Claude

(39:00) Closing thoughts

—

Referenced:

• Salesforce: https://www.salesforce.com/

• Haohan Wang’s post on X: https://x.com/HaohanWang/status/194741703347975783

• How Staff Engineers approach leading remote teams with Cassia Scheffer: https://tuple.app/distributed/how-staff-engineers-approach-leading-remote-teams-with-cassia-scheffer-from-wealthsimple

• Creating High-Performing Remote Engineering Teams with Carlos Rosão: https://tuple.app/distributed/creating-high-performing-remote-engineering-teams-with-carlos-rosao-from-newstore

• 10 Principles for Architecture at Salesforce: https://engineering.salesforce.com/10-principles-for-architecture-at-salesforce-82105d5399a8/

• Brad Arkin on LinkedIn: https://www.linkedin.com/in/brad-arkin/

• Co-Intelligence: Living and Working with AI: https://www.amazon.com/Co-Intelligence-Living-Working-Ethan-Mollick/dp/059371671X

In this episode of Distributed, host Jack Hannah speaks with Jori Lallo, co-founder of Linear, to unpack how he and his co-founders shaped one of the most opinionated products in software. They discuss why the team built a product before a business, the principles behind the Linear Method, and how feedback and work trials define Linear’s culture.

The conversation also explores the realities of running a team split across Europe and the U.S., the role of in-person meetups, and how AI is reshaping both Linear’s workflows and the future of collaboration.

For anyone interested in remote work, intentional culture, and the next chapter of software building, this is a conversation worth hearing.

—

Where to find Jori Lallo:

• X: https://x.com/jorilallo

• LinkedIn: https://www.linkedin.com/in/jorilallo/

—

Where to find Jack Hannah:  

• LinkedIn: https://www.linkedin.com/in/jack-hannah/

• Website: https://tuple.app/

—

Timestamps:

(00:00) Intro

(01:08) Why Linear’s founders built a product before a business

(03:40) How the co-founders of Linear met

(05:01) Shaping Linear’s opinionated philosophy and building tools for modern teams

(09:40) Why the Linear Method still resonates today and where it needs a refresh

(11:45) The role of feedback in Linear’s product culture

(15:40) How Linear approaches hiring

(18:05) The secret ingredient they look for when hiring

(22:18) How Linear operates as a fully remote company 

(24:51) How Linear balances synchronous and asynchronous work across Europe and the U.S.

(27:12) The importance of in-person meetups and social connection

(29:38) How work trials act as a filter for alignment and fit

(31:08) How AI is changing collaboration and work at Linear

(37:31) Closing thoughts

—

Referenced:

• Linear: https://linear.app/

• Karri Saarinen on X: https://x.com/karrisaarinen/ 

• Tuomas Artman on X: https://x.com/artman 

• Y Combinator: https://www.ycombinator.com/

• The Linear Method: Practices for building: https://linear.app/method

• Why and how we do work trials at Linear: https://linear.app/now/why-and-how-we-do-work-trials-at-linear

• The heirloom tomato org chart (Nan Yu, Head of Product, Linear): https://www.youtube.com/watch?v=I4vvBidQcck  

• Clerk Cofounder & CEO on how to build a company that delivers incredible DX: https://tuple.app/distributed/clerk-cofounder-and-ceo-on-how-to-build-a-company-that-delivers-incredible-dx

In this episode of the Distributed podcast, host Jack Hannah talks with Jeff Langr, a software coach, author, and longtime XP advocate. Jeff has helped teams across dozens of companies navigate Agile, pairing, and collaborative programming practices.

Jack and Jeff dig into the surprising downsides of traditional agile software development and how mob programming offers a more inclusive and sustainable way to work. Jeff also shares what works (and doesn’t) about return-to-office efforts and why many organizations are failing to support effective remote collaboration.

Highlights:

• The two rules for making mob programming effective
• Rotations, engagement, and how to avoid team lead dominance
• How Jeff helped skeptics embrace mobbing

In this episode, we cover:

(00:00) – Kicking things off with Jeff Langr

(01:20) – Why mob programming beats solo and pair workflows

(04:15) – Reducing work in progress to boost team flow

(06:12) – The hidden time costs of traditional agile rituals

(08:53) – What makes mob programming a bad choice

(14:26) – How to keep everyone engaged (in-person vs remote)

(18:35) – The two rules every mob team should follow

(23:48) – Navigating fear and vulnerability in mobbing

(24:26) – Turning a skeptic into a mob programming advocate

(25:41) – Why return-to-office pushes often reflect leadership failure



Where to connect further:

Connect with Jeff Langr on LinkedIn and his website

Follow Tuple

Want to hear more? Check out distributed.fm

Connect with Jack Hannah

In this episode of the Distributed podcast, host Jack Hannah sits down with Woody Zuill, the programmer, coach, and speaker best known for popularizing mob programming.

Rather than rehashing the basics of mob programming, Woody talks about what it means to focus on effectiveness instead of productivity and what management gets all wrong. Woody shares insights from decades of experience coaching teams around the world and explains how to create environments that allow real collaboration to flourish.

Highlights:

• The philosophy behind mob programming and software teaming
• Why effectiveness matters more than productivity
• How AI affects how teams collaborate

In this episode, we cover:

(00:00) – Kicking things off with Woody Zuill

(01:10) – The Robert Henri quote that frames Woody’s philosophy

(03:16) – Letting teams self-organize and experiment with how they work freely

(07:41) – Cutting a 500-bug backlog to 17 by working closely as a team

(10:11) – Why separating teams by specialty fragments doesn’t work

(12:22) – Productivity vs. effectiveness and who software is really for

(14:55) – Figuring out what matters through doing, not managing

(17:26) – Will AI replace teams or change how they collaborate?

(19:12) – The role of AI in software development and teamwork

(22:03) – Woody’s advice to new engineers and how to shape better workplaces

References

Jack’s favorite talk from Woody: Mob Programming: A Whole Team Approach

Lean Software Development by Mary Poppendieck and Tom Poppendieck

The Art of Computer Programming by Donald Knuth

The 4 Stages of Psychological Safety by Timothy Clark

Teaming by Amy Edmondson

Where to connect further:

Connect with Woody Zuill on LinkedIn and on his website

Follow Tuple

Want to hear more? Check out distributed.fm

Connect with Jack Hannah

In this episode of Distributed, host Jack Hannah talks to Chris Lucian and Austin Chadwick, the creators of the Mob Mentality Show and longtime engineering leaders at Hunter Industries. Chris, Director of Global Software Development, and Austin, Distinguished Engineer, reflect on mob programming and how practices spread. They open up about what it takes to protect team culture while growing, discuss lessons from their 300+ videos on mob programming and agile, and how AI is just another member of the mob.

Highlights:

• How mob programming went from one team’s experiment to org-wide practice
• What Chris and Austin learned from publishing 300+ episodes on agile and XP
• How AI fits into social coding and the future of pairing and mobbing

In this episode, we cover:

(00:00) – Kicking things off with Chris Lucian and Austin Chadwick

(01:52) – Rearranging cubicles to make pairing possible

(03:09) – The first mob and why it worked

(05:01) – Repairing a wonky relationship with the product owner

(06:14) – Austin’s first mob and learning a new language on the fly

(07:41) – The Mob Mentality Show origin story

(09:22) – How Chris and Austin keep their episodes lean and sustainable

(12:17) – Diffusion of innovation and spreading practices

(15:18) – AI-generated code with domain languages

(18:41) – Growing the mob through cellular division while keeping culture

(24:49) – What to do when there are no internal XP mentors

(28:12) – Using AI like another member of the mob

(32:26) – Will AI replace pair and mob programming?



References

The Mob Mentality Show

Human & AI Collaboration in Mob Programming with Aaron Griffith and Parker Barrett

Where to connect further:

Connect with Chris Lucian on LinkedIn

Connect with Austin Chadwick on LinkedIn 

Follow Tuple

Want to hear more? Check out distributed.fm

Connect with Jack Hannah

In this episode of the Distributed podcast, host Jack Hannah is joined by Benji Weber, Cofounder & CTO at Geordie AI, to discuss leadership and autonomy in engineering teams. Benji shares his unique perspective on how managers can empower teams to take control of their work. They explore how the paradox of giving control plays out in practice and what it means for team ownership and performance.

Highlights:

- How managers can create environments that foster ownership

- The challenges of balancing control with autonomy in fast-growing teams

- How Benji empowers teams through curiosity and gentle nudging

In this episode, we cover:

(00:00) – Introduction to Benji Weber

(01:23) – Benji’s take on professional pride and leadership

(03:54) – Mindgard’s small team setup and remote-first approach

(04:55) – Balancing in-person work with a remote-first culture

(06:12) – The paradox of giving control to teams

(07:07) – Coercion vs. nudging in leadership practices

(08:39) – What it looks like to empower teams through curiosity

(10:56) – Creating an environment for teams to own their work

(14:17) – Tackling organizational reliability challenges with team autonomy

(16:22) – Fostering agency in teams through self-discovery and retrospectives

(18:15) – Why pair programming can be a powerful tool in small teams

(23:46) – Approaching continuous integration and the value of real CI

(26:43) – The trade-offs between consistency and flexibility in team practices

(29:38) – Finding the right balance between synchronous and asynchronous work.

Where to connect further:

Connect with Benji Weber on LinkedIn (https://www.linkedin.com/in/benjiweber/) and on his website (https://benjiweber.co.uk/)

Follow Tuple: https://x.com/tuple

Want to hear more? Check out http://distributed.fm

Connect with Jack Hannah: https://www.linkedin.com/in/jack-hannah/

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 succeed
• Lessons from scaling change across 1,000+ dev organizations
• The 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

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 happiness
• Salesforce'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

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 beyond
• How Obie and Shopify use AI
• Reflections 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

In this episode of the Distributed podcast, host Jack Hannah chats with Thomas Paul Mann, cofounder and CEO of Raycast, the native productivity tool and extendable launcher. They cover how Raycast leverages community, ships such high quality product consistently, and approaches hiring. Jack actually spoke with Thomas the day after Raycast released their iOS app, so the episode starts with a pretty raw reflection on this major milestone before diving into the rest.

Highlights:

• Thomas’s reaction to releasing iOS
• How Raycast leverages community over data
• What it takes to sustain Raycast’s biweekly shipping cadence and 
• How dogfooding drives product polish and reliability

In this episode, we cover:

(00:00) – Opening the conversation with Thomas Paul Mann

(01:18) – Launching iOS with zero pre-hype

(07:19) – Why iOS came before Windows

(09:53) – Going remote during COVID

(14:27) – Building an effective remote team

(16:09) – Why 80% of Raycast is product

(17:45) – Hiring in waves to avoid overgrowth

(19:54) – The power of referral-based hiring

(21:50) – How feedback beats metrics at Raycast

(27:24) – Inside their biweekly shipping rhythm

(32:55) – Using nightly builds to polish UX

Where to connect further:

Connect with Thomas Paul Mann on X

Follow Raycast on X or join the Slack community

Follow Tuple

Want to hear more? Check out distributed.fm

Connect with Jack Hannah