Distributed.

Tim Ottinger, a Senior Consultant at Industrial Logic and the Agile Otter, dives into rethinking software development practices. He discusses the pitfalls of solo work and the myths of efficiency in traditional teams. Tim highlights the power of swarm boards for enhanced remote collaboration and emphasizes boosting first-time through rates as a key productivity metric. The conversation also touches on the limitations of AI in coding. Tim advocates for small collaborative experiments to improve workflows and encourages raising team abilities instead of lowering pipeline standards.

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 qualityIn 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 assistantsReferencesApproval Tests and the weekly Approval Tests EnsembleChatGPT & Copilot are NOT Refactoring ToolsWhere to connect further:Connect with Emily Bache on LinkedIn and Samman Technical Coaching SocietyFollow TupleWant to hear more? Check out distributed.fmConnect with Jack Hannah

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 innovationIn 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 connectionReferencesWorking Effectively with Legacy Code by Michael FeathersAgile Coaching by Rachel Davies and Liz SedleyWhere to connect further:Connect with Matt Wynne on LinkedIn and his WebsiteFollow TupleWant to hear more? Check out distributed.fmConnect with Jack Hannah

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 adaptabilityIn 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 stepsWhere to connect further:Connect with Colin Sidoti on X and ClerkFollow TupleWant to hear more? Check out distributed.fmConnect with Jack Hannah

Ryan Bergman, Principal Engineer at John Deere, delves into how Extreme Programming (XP) rescued a failing startup, emphasizing collaboration and improved code quality. He champions pair programming for team cohesion and discusses the challenges of remote collaboration. Ryan also shares insights on managing large-scale software development, the importance of Behavior-Driven Development (BDD) in boosting team confidence, and fostering trust through clear communication. His journey from graphic arts to engineering offers a unique perspective on the tech industry.

Anthony Eden started DNSimple as a remote first, mostly asynchronous company in 2010 before it was cool.In this episode of the Distributed podcast, host Jack Hannah sits down with Anthony, Founder and CEO, to discuss the intricacies of remote-first companies. Anthony shares his journey of building DNSimple as a remote-first company, highlighting how asynchronous communication and flexible structures foster a thriving tech culture. The discussion touches on what shapes a successful organization and the challenges he’s faced over the years.Anthony also shares his experience with Shape Up and how it’s improved his team’s productivity and trust in each other.Highlights:Remote work norms and fostering collaboration across different time zones Anthony’s journey with Shape UpHow to facilitate trust among team membersDNSimple’s culture of collaborationIn this episode, we cover:(00:00) - Kicking things off with Anthony Eden(00:55) - Founding DNSimple: Anthony’s journey to remote work(02:47) - Embracing remote work: the time zone challenge(04:02) - Company growth and team structure at DNSimple(06:56) - The shift to Shape Up: solving development challenges(10:42) - Facilitating trust and commitments in remote teams(16:06) - Asynchronous collaboration tools(21:45) - Aligning remote work practices: learning from experiments(31:20) - The human side of remote work: building emotional connections(35:43) - Conclusion: looking ahead with a growth mindset in remote workReferences mentioned:DNSimple’s time tracking experimentShape UpWhere to connect further:Connect with Anthony Eden on LinkedInFollow TupleWant to hear more? Check out distributed.fmConnect with Jack Hannah

Trust, collaboration, and adaptability define the best engineering teams.In this episode of the Distributed podcast, host Jack Hannah sits down with Pavel Hubich, Software Engineer at Spotify, to explore the realities of remote and hybrid work. Pavel shares his journey navigating career shifts, relocations, and the challenges of distributed collaboration. He opens up about why he prefers working in person, how hybrid work can create communication bubbles, and what teams can do to foster trust despite physical distance.They also discuss the impact of structured rituals like daily standups and the Swedish tradition of Fika, how mob programming transformed his team’s efficiency, and why balancing autonomy with connection is critical for engineers working remotely.Highlights:Navigating career transitions from frontend to backend engineering while relocating across continentsWhy hybrid work can unintentionally create communication bubbles—and how teams can bridge the gapsThe role of standups, casual rituals, and structured collaboration in building trust remotelyUsing mob programming and Architecture Golf to reduce context switching and improve team alignmentFinding a balance between focus, flexibility, and human connection in a remote-first worldIn this episode, we cover:(00:00) – Kicking things off with Pavel Hubich(01:24) – From EPAM to Spotify: Pavel’s software journey(05:18) – Relocating to San Francisco for on-site work(08:01) – Why Pavel prefers the office over remote(13:56) – Rituals and loading screens: creating mental transitions(16:03) – The real challenge of remote work: earning trust(18:24) – Standups and Fika: building connection remotely(21:45) – When high output doesn’t equal team cohesion(26:29) – How mob programming brought the team back together(29:53) – Using architecture golf to share context and collaborate(34:29) – Making hybrid work without creating bubbles(36:25) – Building trust without burning outWhere to connect further:Connect with Pavel Hubich on LinkedInFollow TupleWant to hear more? Check out distributed.fmConnect with Jack Hannah

How do you foster connection and collaboration in a remote-first world?In this episode of the Distributed podcast, host Jack Hannah sits down with Nick Cash, Senior Vice President & Head of Technology at Jam City, to explore the unique challenges and opportunities of leading a hybrid team across the globe. Nick shares insights into Jam City’s hub-and-spoke organizational structure, the importance of reducing friction in communication, and the value of synchronous collaboration. He also discusses strategies for empowering engineers, fostering connections across teams, and building a culture of trust and innovation in a remote-first environment.Highlights:Jam City’s hybrid approach to remote-first work and global team dynamicsReducing friction with clear processes and effective communication toolsThe importance of synchronous collaboration for solving complex problemsBuilding connections through programs like Jam City UniversityHow fostering team relationships leads to better project outcomesIn this episode, we cover:(00:00) – Kicking Things Off With Nick Cash(04:44) – Optimizing Product Lifecycle and Team Agility(08:35) – Integrating Processes with Flexibility(12:34) – Fostering Occasional Team Interactions(14:40) – Balancing Mentorship and Independence(19:06) – Effective Team Communication Boosts Productivity(22:44) – Fostering Success at Jam City(25:44) – Leveraging Curiosity for Networking Success(27:17) – Jam City's Global Talent Strategy(32:23) – Exploring Meetings vs. Problem-Solving Calls(34:37) – Comparing In-Person and Virtual Collaboration PerceptionsWhere to connect further:Connect with Nick Cash on LinkedInMore about Jam CityFollow TupleWant to hear more? Check out distributed.fmConnect with Jack Hannah

What happens when a fully remote team prioritizes speed, flexibility, and customer feedback?In this episode of the Distributed podcast, Host Jack Hannah talks to Sumeet Jain, Head of Engineering at Sublime Security, about how they manage one-week development cycles to stay agile and responsive to their customers’ needs. Sumeet shares how the team’s reliance on Slack and Notion streamlines workflows and minimizes friction, helping engineers stay connected even across time zones.They also discuss how making work visible, listening to customers, and maintaining a balance between speed and quality are key to Sublime’s success in a fast-paced remote environment.Highlights:Why a one-week development cycle gives Sublime a competitive edgeHow the team uses Slack and Notion to manage tasks and streamline communicationThe importance of making work visible to foster camaraderie in a remote teamHow prioritizing customer feedback drives development decisionsMaintaining speed and focus while ensuring quality in a rapid delivery environmentIn this episode, we cover:(00:00) – Kicking things off with Sumeet Jain(01:13) – Catching the software bug with a Penny Hardaway fan site(02:21) –  Running a fully remote team across North America(03:20) – Why Sublime chose one-week engineering cycles(07:00) – Inside the Monday planning ritual and company alignment(11:39) – How customer feedback drives weekly priorities(14:08) – Rethinking under promise and over deliver culture(19:02) – Principles behind Sublime’s lightweight operations(22:59) – Using emoji reactions to create tasks in Slack(28:47) – Organizing work through “T channels”(34:01) –  Sumeet’s favorite remote work gear and why air quality mattersProducts mentioned:UGMONK Analog Wood Card HolderAranet4 CO2 MonitorWhere to connect further:Connect with Sumeet Jain on LinkedInFollow TupleWant to hear more? Check out distributed.fmConnect with Jack Hannah

How do you transition from a solo founder to leading a thriving remote team?In this episode of the Distributed podcast, Host Jack Hannah sits down with Chris Oliver, Founder of GoRails and Host of the Remote Ruby podcast, to discuss his journey from working solo to building a successful three-person remote team. Chris shares a candid look at how he overcame the challenge of scaling a business, the importance of asynchronous communication, and how he created a system that fosters remote collaboration. Highlights:Strategies for transitioning from solo work to team leadershipBalancing asynchronous and synchronous collaboration for remote teamsHow Chris built a sustainable business that works for him, not the other way aroundThe tools and processes that enable GoRails to thrive remotelyIn this episode, we cover:(00:00) – Kicking things off with Chris Oliver(00:42) – The origin of GoRails: From tutorials to product market fit(04:03) – Challenges of solopreneurship and the decision to expand(06:28) – Adapting processes for a team environment(09:27) – The value of pair programming in remote work(12:46) – Balancing asynchronous and synchronous communication(18:35) – Creating a calm company culture at GoRails(37:16) – Encouraging entrepreneurship and lessons from experienceReferenced:Railscasts by Ryan BatesMichael Gerber’s Book: The E-Myth on AmazonWhere to connect further:Connect with Chris Oliver on X and GitHubMore about GoRailsFollow TupleWant to hear more? Check out distributed.fmConnect with Jack Hannah