Distributed.

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

In this engaging discussion, Nick Cash, Senior VP & Head of Technology at Jam City, shares his expertise in remote leadership. He delves into Jam City's innovative hub-and-spoke model for global teams and emphasizes the necessity of reducing communication friction. Nick also highlights the value of synchronous collaboration in problem-solving and the importance of programs like Jam City University for fostering connections. Lastly, he discusses how nurturing team relationships leads to enhanced project outcomes and a thriving culture of trust and creativity.

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

Mike Bland, a Developer Experience Platform Architect at EngFlow with a rich background at Google and Apple, shares his insights on forging effective remote work cultures. He discusses the grassroots origins of Google's Testing Grouplet and the quality culture initiative from Apple, revealing how these experiences inform his strategies today. Mike emphasizes the critical role of intentional communication and the power of trust within distributed teams. He also highlights the challenges of balancing autonomy and collaboration in remote environments.

Rachel Trana, Senior Engineering Manager at Grainger with nearly 15 years in software and a PhD in applied math, shares valuable insights on hybrid work strategies. She emphasizes the importance of effective project kickoffs and the benefits of pair programming in fostering communication. Rachel discusses tackling onboarding challenges and the need for clear status updates to keep teams aligned. With practical advice for both leaders and team members, she offers innovative solutions to navigate the complexities of remote collaboration.

Carlos Rosão, Director of Software Engineering at NewStore, discusses creating high-performing remote engineering teams. He emphasizes the balance between autonomy and standardization, highlighting how pair programming fosters collaboration and reduces miscommunication. Carlos shares insights on prioritizing customer feedback for product innovation and the significant role of in-person meetups in building trust and cohesion. He offers practical strategies for improving communication and ownership in distributed teams, making remote work not just effective, but empowering.

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