Distributed.

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

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

Dave Farley, a pioneering software engineer and author renowned for his expertise in continuous delivery, delves into the crucial role of human connection in software development. He champions pair programming as a key practice for boosting productivity and code quality. Farley discusses the trade-offs of remote work, emphasizing the importance of building and maintaining trust among distributed teams. He also explores AI's evolving impact on software engineering, warning against neglecting teamwork in the face of technological advancements.

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 valentina.servile@gmail.com More about ThoughtworksFollow TupleWant to hear more? Check out distributed.fmConnect with Jack Hannah

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