Distributed.

Antony Marcano is the founder of RiverGlide and an engineering leader known for building teams that reach the Elite tier of the DORA metric for software delivery performance. In this episode of Distributed, host Jack Hannah talks with Antony about what distinguishes those teams and how AI is reshaping software delivery.Antony explains why AI-augmented coding often amplifies existing team dynamics, accelerating work upstream of bottlenecks and sometimes harming end-to-end performance. He discusses why humans must still maintain codebases, how overreliance on AI can reduce collaboration, and why leaders should measure delivery performance before adopting tools under top-down pressure.They also explore what return-to-office mandates often miss about remote collaboration, how elite remote-first teams operate, and why DORA remains a useful starting point for understanding performance in the AI era.—Where to find Antony Marcano:• LinkedIn: https://www.linkedin.com/in/antonymarcano • Website: https://antonymarcano.com • Bluesky: https://bsky.app/profile/antonymarcano.bsky.social —Where to find Jack Hannah:  • LinkedIn: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/in/jack-hannah/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠• Website: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://tuple.app/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠—Timestamps:(00:00) Intro(01:07) The four DORA metrics(03:08) What elite status means(08:50) What excites Antony about AI(12:09) What concerns Antony about AI(15:56) Removing delivery bottlenecks(18:49) AI’s impact on collaboration(22:02) Risks of relying entirely on AI code(27:11) Why collaboration matters in software teams (31:19) Navigating top-down pressure to adopt AI(36:45) Why DORA is a good starting point(39:04) Return-to-office mandates(42:30) Characteristics of elite remote-first teams(47:52) METR study on AI and perceived productivity(50:15) Rapid fire round —Referenced:• RiverGlide: https://riverglide.com• DORA’s software delivery performance metrics: https://dora.dev/guides/dora-metrics• Waterfall Methodology: A Comprehensive Guide: https://www.atlassian.com/agile/project-management/waterfall-methodology• Is Your AI assisted Coding Strategy Quietly Backfiring?: https://www.youtube.com/watch?v=dQ1apxgvOa0• 2025 DORA State of AI-assisted Software Development Report: https://cloud.google.com/resources/content/2025-dora-ai-assisted-software-development-report• OpenClaw: https://openclaw.ai• OpenClaw (formerly Moltbot, Clawdbot) May Signal the Next AI Security Crisis: https://www.paloaltonetworks.com/blog/network-security/why-moltbot-may-signal-ai-crisis• Performance at the Limit: Business Lessons from Formula 1 Motor Racing: https://www.amazon.com/Performance-Limit-Business-Lessons-Formula/dp/0521844002• Measuring the Impact of Early-2025 AI on Experienced Open-Source Developer Productivity: https://arxiv.org/abs/2507.09089• Extreme Programming: A gentle introduction: http://www.extremeprogramming.org• Extreme Programming Explained: Embrace Change: https://www.amazon.com/Extreme-Programming-Explained-5-Oct-1999-Paperback/dp/B011T86NIY• Machine learning expert on the 3 skills that matter most in the AI age: https://tuple.app/distributed/machine-learning-expert-on-the-3-skills-that-matter-most-in-the-AI-age• Jason Gorman on LinkedIn: https://www.linkedin.com/in/jasongorman• The AI-Ready Software Developer – Index: https://codemanship.wordpress.com/2025/10/30/the-ai-ready-software-developer-index• Dave Farley’s blog: https://www.davefarley.net• Kevlin Henney’s website: https://kevlin.tel

In this episode of Distributed, Jack Hannah speaks with Scott Jones, Head of Engineering for Service Delivery at Stash, about building complex systems in a remote-first environment and why real-time collaboration matters more than ever.Scott reflects on helping build Stash’s core banking platform in just one year, breaking down what building a bank actually means from an engineering perspective. He explains how the work was structured across teams, why individual heroics fall apart at scale, and how frequent synchronous coordination helped the team move fast without breaking things.The conversation introduces Scott’s idea of “aggressive huddling,” a practice of using real-time communication with tools like Tuple to simulate in-office collaboration. Through concrete stories, including a critical migration issue resolved before customers noticed, Scott shows how early human coordination can prevent costly failures.The episode also explores how AI is changing engineering work at Stash. As execution becomes faster, Scott argues that collaboration, project management, and problem framing are becoming core engineering skills, and that AI increases the need for human alignment rather than reducing it.—Where to find Scott Jones:• LinkedIn: https://www.linkedin.com/in/scott-jones-bab7b713• Website: https://www.stash.com/ —Where to find Jack Hannah:  • LinkedIn: ⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/in/jack-hannah/⁠⁠⁠⁠⁠⁠⁠⁠⁠• Website: ⁠⁠⁠⁠⁠⁠⁠⁠⁠https://tuple.app/⁠⁠⁠⁠⁠⁠⁠⁠⁠—Timestamps:(00:00) Intro(01:32) What it takes to build a bank (05:24) Why the one-year timeline didn’t feel daunting(08:52) Structuring the work across teams (11:14) “Aggressive huddling” on Tuple(14:08) How real-time huddling saved a failing migration(18:47) How real-time coordination works day to day(22:42) Why postmortems can be a collaboration red flag(25:46) How engineers at Stash are using AI today(31:37) The skills that engineers need now (33:50) Why AI tools demand more collaboration(36:07) How time is allocated in an AI-driven workflow(38:33) The future of human-AI collaboration(41:20) Rapid fire round —Referenced:• Stash: https://www.stash.com• Forrest Gump: https://en.wikipedia.org/wiki/Forrest_Gump• Keir Lauritzen on LinkedIn: https://www.linkedin.com/in/keir-lauritzen• Ruby on Rails: https://rubyonrails.org• Test Driven Development: https://martinfowler.com/bliki/TestDrivenDevelopment.html• Uncle Bob Martin on X: https://x.com/unclebobmartin• Justin Martin on LinkedIn: https://www.linkedin.com/in/mythinking• Grok: https://grok.com• Broken Money: Why Our Financial System is Failing Us and How We Can Make it Better: https://www.amazon.com/Broken-Money-Financial-System-Failing/dp/B0CG83QBJ6

In this episode of Distributed, host Jack Hannah sits down with Andrew Stellman, a longtime software engineer, author, and engineering leader who has written multiple widely used software engineering books published by O’Reilly.Andrew reflects on how being forced into remote work after September 11th shaped his thinking about teamwork, what high-performing teams get right about alignment and mission, and why listening carefully is still central to building useful software. The conversation then turns to AI, where Andrew talks about why these tools work best when engineers slow down, think critically, and stay engaged with the code they are creating.Andrew also shares five habits that help developers use AI more effectively, why learning to skim and read code matters, and why many of the challenges teams face today are not new, even if the tools are.—Where to find Andrew Stellman:• X: https://x.com/AndrewStellman • LinkedIn: https://www.linkedin.com/in/andrewstellman • Linktree: https://linktr.ee/andrewstellman—Where to find Jack Hannah:  • LinkedIn: ⁠⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/in/jack-hannah/⁠⁠⁠⁠⁠⁠⁠⁠• Website: ⁠⁠⁠⁠⁠⁠⁠⁠https://tuple.app/⁠⁠⁠⁠⁠⁠⁠⁠—Timestamps: (00:00) Intro(01:27) Andrew’s first experience working remotely (03:57) Why remote work depends on shared understanding(06:54) Why trust is so hard on teams(08:50) What high-performing teams have in common (12:03) Turning user needs into buildable requirements(15:34) How to get better at explaining problems(16:38) Why Andrew believes AI improves software(19:42) Why prompt engineering is really requirements engineering(24:20) How LLMs make shared understanding cheaper(26:49) Why skimming is a critical AI-era skill(30:05) Five habits for getting more out of AI(35:40) A real example of the rehash loop(37:59) Why software’s hardest problems haven’t changed—Referenced:• Jennifer Greene on LinkedIn: https://www.linkedin.com/in/jennifergreene• Applied Software Project Management: https://www.amazon.com/Applied-Software-Project-Management-Stellman/dp/0596009488• Learning Agile: Understanding Scrum, XP, Lean, and Kanban: https://www.amazon.com/Learning-Agile-Understanding-Scrum-Kanban/dp/1449331920• Beautiful Teams: Inspiring and Cautionary Tales from Veteran Team Leaders: https://www.amazon.com/Beautiful-Teams-Inspiring-Cautionary-Veteran/dp/0596518021• Head First C#: A Learner's Guide to Real-World Programming with C# and .NET: https://www.amazon.com/Head-First-Learners-Real-World-Programming/dp/1098141784• On Writing: A Memoir Of The Craft: https://www.amazon.com/Writing-Memoir-Craft-Stephen-King/dp/1982159375• Save The Cat! The Last Book on Screenwriting You'll Ever Need: https://www.amazon.com/Save-Last-Book-Screenwriting-Youll/dp/1932907009• Why Projects Fail: https://www.stellman-greene.com/Why_Projects_Fail.pdf• Anthropic co-founder on quitting OpenAI, AGI predictions, $100M talent wars, 20% unemployment, and the nightmare scenarios keeping him up at night | Ben Mann: https://www.lennysnewsletter.com/p/anthropic-co-founder-benjamin-mann• Beyond Vibe Coding: From Coder to AI-Era Developer: https://www.amazon.com/Beyond-Vibe-Coding-AI-Era-Developer/dp/B0F6S5425Y• The Cognitive Shortcut Paradox: https://www.oreilly.com/radar/the-cognitive-shortcut-paradox • The Sens-AI Framework: Teaching Developers to Think with AI: https://www.oreilly.com/radar/the-sens-ai-framework/

What does craftsmanship look like in an async-first, remote company?In this episode of Distributed, host Jack Hannah sits down with Steve Schoeffel, co-founder of Whimsical, to talk about async-first work, craftsmanship, and the tradeoffs of running a fully remote company. Steve shares how Whimsical creates momentum without constant meetings, why quality lives in the details, and how async-first work shapes both the product and the company culture.Steve also reflects on the harder, more personal side of the work. He talks candidly about co-founder misalignment, the strain of leadership during periods of uncertainty, and what it’s been like to learn to hold work more loosely over time.They also dig into the return-to-office push and why Steve remains convinced that remote work, done well, is worth fighting for.—Where to find Steve Schoeffel:• LinkedIn: https://www.linkedin.com/in/steveschoeffel—Where to find Jack Hannah:  • LinkedIn: ⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/in/jack-hannah/⁠⁠⁠⁠⁠⁠⁠• Website: ⁠⁠⁠⁠⁠⁠⁠https://tuple.app/⁠⁠⁠⁠⁠⁠⁠—Timestamps:(00:00) Intro(01:02) An overview of Whimsical (02:02) The size of Whimsical’s team and how it operates across time zones(03:08) What the Whimsical Way is and how it shows up in practice (04:58) Why Whimsical is async-first and what that looks like in practice(10:49) How Whimsical maintains energy and connection in async work(13:59) Craftsmanship as a core value at Whimsical(18:21) How Whimsical pursues “insanely great” work(24:14) What’s been hardest about running a remote company(28:24) How Steve realized he and his co-founder were misaligned(32:08) How Steve is learning to detach from work and care for himself(36:32) Why Steve remains pro–remote work amid big tech’s return-to-office push—Referenced:• Whimsical: https://whimsical.com• The State of Async (formerly The Whimsical Way): https://whimsical.com/blog/state-of-async-2026• Kaspars Dancis on LinkedIn: https://www.linkedin.com/in/kasparsd • How async work inspires craftsmanship: https://whimsical.com/blog/how-async-work-inspires-craftsmanship• Development cycles, process, and tooling: https://tuple.app/distributed/head-of-engineering-at-sublime-security-on-development-cycles-process-and-tooling-with-sumeet-jain• Craftsmanship, the heart of Whimsical: https://whimsical.com/blog/craftsmanship-the-heart-of-whimsical• Frank Slootman on LinkedIn: https://www.linkedin.com/in/frankslootman• Shapeup: https://basecamp.com/shapeup

Why does so much software still feel broken, even after years of new tools and processes?On this episode of Distributed, host Jack Hannah sits down with Scott Hanselman, Vice President of Developer Community at Microsoft, to explore how fear-driven development, speed-first incentives, and short-term thinking continue to shape modern software.Scott reflects on why craftsmanship has become rare, how some teams still manage to do quality work, and how today’s engineering systems influence the outcomes we see. The conversation also examines how AI is changing the day-to-day experience of engineers, why junior developers need much more support, and what stronger apprenticeship models could look like in practice. Scott shares ideas for investing in people over the long term and building meaningful communities across distributed teams. This episode offers a clear lens on what it takes to build better software by investing in people and systems together.—Where to find Scott Hanselman:• X: https://x.com/shanselman • LinkedIn: https://www.linkedin.com/in/shanselman • Blog: https://www.hanselman.com/blog• Newsletter: https://hanselman.substack.com• The Hanselminutes Podcast:  https://www.hanselminutes.com • Scott and Mark Learn To Podcast: https://www.youtube.com/playlist?list=PL0M0zPgJ3HSf4XZvYgZPUXgSrfzBN26pf—Where to find Jack Hannah:  • LinkedIn: ⁠⁠⁠⁠⁠⁠https://www.linkedin.com/in/jack-hannah/⁠⁠⁠⁠⁠⁠• Website: ⁠⁠⁠⁠⁠⁠https://tuple.app/⁠⁠⁠⁠⁠⁠—Timestamps:(00:00) Intro(01:25) Why so much software feels broken and why it persists(03:38) The outlier companies focused on quality software(04:30) What software craftsmanship looks like and why it’s rare(08:18) How to reduce fear-driven development(11:50) How AI reflects the flaws in today’s software practices(12:46) How AI affects senior and junior engineers differently(17:03) Rethinking the mentorship model for junior engineers(19:11) Best practices for a structured apprenticeship program (21:43) Delegate, verify, and integrate: a model for managing AI and junior engineers(22:05) Why pair programming isn’t enough on its own(27:07) The case for long-term investment in people(29:54) Where big tech has fallen short and created division(32:52) The indie web and alternatives to platform-driven tech(34:30) How to build community across distributed teams(38:20) Rapid fire round —Referenced:• Everything’s broken and nobody’s upset: https://www.hanselman.com/blog/everythings-broken-and-nobodys-upset• Instapaper: https://www.instapaper.com• Pocket: https://heypocket.com• 1Password: https://1password.com• Cabel Sasser’s website: https://cabel.com• Visual Studio Code: https://code.visualstudio.com • Boeing: https://www.boeing.com• Mark Russinovich on LinkedIn: https://www.linkedin.com/in/markrussinovich• Tech Promised Everything. Did it deliver? | Scott Hanselman | TEDxPortland: https://www.youtube.com/watch?v=dVG8W-0p6vg• IntelliSense: https://code.visualstudio.com/docs/editing/intellisense• Usenet: https://en.wikipedia.org/wiki/Usenet• POSSE: https://indieweb.org/POSSE• DuckDuckGo: https://duckduckgo.com• Amanda Silver on LinkedIn: https://www.linkedin.com/in/amandaksilver• Brain, Bytes, Back, Buns - The Programmer's Priorities: https://www.hanselman.com/blog/brain-bytes-back-buns-the-programmers-priorities• WeWork: https://www.wework.com• Simon Willison’s blog: https://simonwillison.net

On this episode of Distributed, host Jack Hannah sits down with Ivett Ördög, a 35-year software veteran and creator of Lean Developer Experience (aka Lean Poker), to talk about what it really takes for engineers to grow their impact. Ivett argues that communication, continuous delivery, and delivering value early are not soft add-ons but essential engineering skills that determine how far developers can go.Together, they break down how remote work can create better environments for deep focus and well-being, why strong communication skills often determine the jump from mid-level to staff, and how developers at any stage can begin practicing them. Ivett also shares when rewrites actually make sense, how to communicate them to management, and why continuous delivery gives teams the feedback they need to build the right thing.The episode offers clear, tactical guidance for any engineer looking to level up, advocate for better ways of working, and deliver value earlier and more often.—Where to find Ivett Ördög:• LinkedIn: https://www.linkedin.com/in/ivett-%C3%B6rd%C3%B6g-03aa9035/ • Website: https://www.ivettordog.com —Where to find Jack Hannah:  • LinkedIn: ⁠⁠⁠⁠⁠https://www.linkedin.com/in/jack-hannah/⁠⁠⁠⁠⁠• Website: ⁠⁠⁠⁠⁠https://tuple.app/⁠⁠⁠⁠⁠—Timestamps:(00:00) Intro(01:17) The philosophy behind the Lean Developer Experience (02:24) Why Ivett now believes remote work produces better outcomes(06:45) Why people overlook the benefits of remote work(08:20) How remote work is customizable for needs and deep focus(11:48) Why communication is essential for developer career growth(14:52) Two communication struggles engineers face and how to begin improving(18:46) Where to find speaking opportunities (19:30) Tips for eager speakers with no stage experience(21:15) When rewrites make sense (28:14) How to communicate a rewrite to management(32:15) Ivett’s definition of continuous delivery (34:02) Examples of continuous delivery that show its value(36:54) How to drive change in a slow-moving organization(40:15) How Lean Developer Experience helps teams practice continuous delivery(42:45) The value of hands-on learning—Referenced:• Lean Developer Experience: https://www.ivettordog.com/leandeveloperexperience• Ted Talks: The Official TED Guide to Public Speaking: https://www.amazon.com/TED-Talks-Official-Public-Speaking/dp/1328710289• How to sell a big refactor or rewrite to the business? - Ivett Ördög - NDC Oslo 2025: https://www.youtube.com/watch?v=wdz90PQ2Ak4• Emily Bache’s Samman coaching website: https://sammancoaching.org• Jez Humble on LinkedIn: https://www.linkedin.com/in/jez-humble• Dave Farley’s Weblog: https://www.davefarley.net

In this episode of Distributed, host Jack Hannah talks with Jesse Wilson, a longtime open-source contributor and Cash App engineer, whose work underpins much of the Java and Android ecosystem. Jesse shares why some of the most rewarding engineering work comes from doing things the right way, even when it’s the hard way.Their conversation dives into the story behind Okio, the I/O library for Android, Java, and Kotlin that’s been downloaded >50 billion times, and what it revealed about craftsmanship, risk-taking, and building for the long term. They also unpack how remote teams can bring back the spark of in-person collaboration by pairing more often, embracing small interruptions, and using shared artifacts to stay aligned.—Where to find Jesse Wilson:• Mastodon: https://cosocial.ca/@jessewilson • LinkedIn: https://www.linkedin.com/in/swankjesse • Blog: https://publicobject.com—Where to find Jack Hannah:  • LinkedIn: ⁠⁠⁠⁠https://www.linkedin.com/in/jack-hannah/⁠⁠⁠⁠• Website: ⁠⁠⁠⁠https://tuple.app/⁠⁠⁠⁠—Timestamps:(00:00) Intro(01:28) Why the quick and bad way is never the right choice(04:07) A story from Okio that shaped Jesse’s engineering philosophy(06:39) How company culture empowered Jesse to build Okio(08:46) The challenges of building Okio(12:40) Why Okio was worth building(15:08) The value of spontaneous collaboration and why interruptions can be good(21:10) Handling friction in distributed teams(27:32) The value of shared responsibilities and scheduled maintenance (31:05) How Jesse balances meetings with time for flow state(35:42) How a shared whiteboard or Google Doc keeps meetings on track (40:52) How shared artifacts guide meetings and make wrap-ups effortless(43:23) Rapid-fire round—Referenced:• Okio: https://square.github.io/okio/ • Writing Code That Lasts Forever: https://publicobject.com/2018/08/28/writing-code-that-lasts-forever• Todoist: https://www.todoist.com• inessential by Brent Simmons: https://inessential.com

As AI reshapes how software is built, what does it actually mean to be a good engineer? Chelsea Troy, who leads Machine Learning Operations at Mozilla and teaches computer science at the University of Chicago, argues that the future of engineering isn’t about typing faster but thinking better.In this episode of Distributed, Chelsea joins host Jack Hannah to unpack the three skillsets that matter most in the age of AI: investigative, evaluative, and innovative thinking. She explains why AI tools still fall short in areas that require human reasoning and judgment, how engineers can uplevel the skills that set them apart, and why collaboration and a solid grounding in computer science remain essential.—Where to find Chelsea Troy:• Website: https://chelseatroy.com• LinkedIn: https://www.linkedin.com/in/chelseatroy—Where to find Jack Hannah:  • LinkedIn: ⁠⁠⁠⁠⁠https://www.linkedin.com/in/jack-hannah/⁠⁠⁠⁠⁠• Website: ⁠⁠⁠⁠⁠https://tuple.app/⁠⁠⁠⁠⁠—Timestamps:(00:00) Intro(01:08) The 3 most underrated skillsets engineers rely on every day(08:45) How an interpreter workshop and a Rust compiler project revealed AI’s limits(14:59) How to level up investigative, evaluative, and innovative skills(21:25) Why collaboration still matters but isn’t a new challenge created by AI(25:38) The value of early career pair programming and why it’s hard but worth it(29:09) Why pairing with an LLM has value but can’t replace human collaboration(34:33) Formal CS degrees vs. nontraditional paths and why studying CS still matters(43:49) Rapid fire round—Referenced:• What can we expect of LLMs as Software Engineers?: https://chelseatroy.com/2025/07/14/what-can-we-expect-of-llms-as-software-engineers• Bob Nystrom’s blog: https://journal.stuffwithstuff.com/• Tim Peters: https://github.com/tim-one • Crafting Interpreters: https://craftinginterpreters.com• Using the Python Interpreter: https://docs.python.org/3/tutorial/interpreter.html• Alan Turing: https://en.wikipedia.org/wiki/Alan_Turing• Ada Lovelace: https://en.wikipedia.org/wiki/Ada_Lovelace

Charity Majors is a writer, speaker, and the co-founder and CTO of Honeycomb, an observability platform for debugging and optimizing distributed systems.In this episode of Distributed, Jack Hannah talks with Charity about the realities of leading and scaling a distributed company. From why remote work is not best for every situation to the communication tax of distributed management, Charity shares what she has learned about building effective teams, fostering trust, and staying connected in a remote environment. She also reflects on her own leadership journey, from CEO back to CTO, and how greater self-awareness and empathy have shaped her approach to work and life.—Where to find Charity Majors:• Bluesky: https://bsky.app/profile/charity.wtf• LinkedIn: https://www.linkedin.com/in/charity-majors/• Website: https://charity.wtf/—Where to find Jack Hannah:  • LinkedIn: ⁠⁠⁠https://www.linkedin.com/in/jack-hannah/⁠⁠⁠• Website: ⁠⁠⁠https://tuple.app/⁠⁠⁠—Timestamps:(00:00) Intro(01:15) Why remote work isn’t best for everything(03:20) What Charity learned from her viral Bluesky post on RTOs(08:33) Why distributed teams need more and better management(11:33) How to get the most from a remote work experience as an engineer (14:30) Why 10x engineers matter less than 10x teams(18:06) How trust and psychological safety drive high-performing teams(20:58) Signs of a healthy organization for job seekers(24:17) Charity’s transition from CEO to CTO and the challenges of down-leveling(26:31) When stepping back in your career can be the right move(30:44) How self-awareness transformed Charity’s approach to leadership and life(34:42) Rapid-fire round —Referenced:• Honeycomb: https://www.honeycomb.io/• Charity’s post on Bluesky about RTO policies: https://bsky.app/profile/charity.wtf/post/3lq4cgak3vk24• How 37signals handles communication, meetings, and setting work boundaries: https://tuple.app/distributed/How-37signals-handles-communication-meetings-and-setting-work-boundaries-with-Rosa-Gutierrez• In Praise of “Normal” Engineers: https://charity.wtf/2025/06/19/in-praise-of-normal-engineers/• Christine Yen on LinkedIn: https://www.linkedin.com/in/christineyen/• Simon Willison’s blog: https://simonwillison.net/• Dr. Cat Hicks' newsletter, Fight for the Human: https://www.fightforthehuman.com/

37signals embraced remote work long before it became mainstream. Its Shape Up framework helped define how remote product teams ship fast, but not every team inside the company follows the same playbook. In this episode of Distributed, host Jack Hannah sits down with Rosa Gutiérrez, Principal Programmer at 37signals and founding board member of the Ruby on Rails Foundation.Rosa takes us inside SEIP (Security, Infrastructure, and Performance), the team responsible for everything from privacy and legacy app maintenance to large-scale infrastructure moves, such as migrating 37signals off the cloud. She shares how a writing-first culture, asynchronous communication, and a flexible, reactive approach let her team thrive outside of the Shape Up model.—Where to find Rosa Gutiérrez:• Bluesky: https://bsky.app/profile/rosa.codes• LinkedIn: https://www.linkedin.com/in/rosagutierrezescudero/• Website: https://rosa.codes/—Where to find Jack Hannah:  • LinkedIn: ⁠⁠https://www.linkedin.com/in/jack-hannah/⁠⁠• Website: ⁠⁠https://tuple.app/⁠⁠—Timestamps:(00:00) Intro(01:18) Rosa’s role at 37signals(04:10) How long-form writing is critical to 37signals’ culture(07:34) How Rosa adapted to 37signals’ asynchronous communication and unique work style(10:00) The benefits of asynchronous communication for focus, flexibility, and easy reference(12:08) Why 37signals suits introverts and how they handle in-person meetups(14:25) Why Shape Up doesn’t fit the kind of work Rosa’s team does(17:41) How Rosa’s team prioritizes incoming issues during on-call rotations(21:22) Why Rosa’s flexible work style makes her a perfect fit for SEIP’s reactive team(26:03) The challenge remote workers face in setting boundaries(27:46) A case for getting out of the house to create a better work-life balance—Referenced:• 37signals: https://37signals.com/• Hey: https://www.hey.com/• Basecamp: https://basecamp.com/• Ruby on Rails: https://rubyonrails.org/• Shape Up: https://basecamp.com/shapeup• Shape Up: Stop Running in Circles and Ship Work that Matters: https://basecamp-goods.com/products/shapeup

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 effectiveRotations, engagement, and how to avoid team lead dominanceHow Jeff helped skeptics embrace mobbingIn 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 failureWhere to connect further:Connect with Jeff Langr on LinkedIn and his websiteFollow TupleWant to hear more? Check out distributed.fmConnect 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 teamingWhy effectiveness matters more than productivityHow AI affects how teams collaborateIn 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 workplacesReferencesJack’s favorite talk from Woody: Mob Programming: A Whole Team ApproachLean Software Development by Mary Poppendieck and Tom PoppendieckThe Art of Computer Programming by Donald KnuthThe 4 Stages of Psychological Safety by Timothy ClarkTeaming by Amy EdmondsonWhere to connect further:Connect with Woody Zuill on LinkedIn and on his websiteFollow TupleWant to hear more? Check out distributed.fmConnect 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 practiceWhat Chris and Austin learned from publishing 300+ episodes on agile and XPHow AI fits into social coding and the future of pairing and mobbingIn 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?ReferencesThe Mob Mentality ShowHuman & AI Collaboration in Mob Programming with Aaron Griffith and Parker BarrettWhere to connect further:Connect with Chris Lucian on LinkedInConnect with Austin Chadwick on LinkedIn Follow TupleWant to hear more? Check out distributed.fmConnect 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/tupleWant to hear more? Check out http://distributed.fmConnect 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 succeedLessons from scaling change across 1,000+ dev organizationsThe engineering rituals that help his teams excel, like meandering syncs and mobbing MondaysIn 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 workReferences: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 websiteFollow TupleWant to hear more? Check out distributed.fmConnect 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 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 passionsReferencesTest Driven Development: By Example by Kent BeckDomain Modeling Made Function by Scott WlaschinWhere to connect further:Connect with James Simone on LinkedIn and on his websiteFollow TupleWant to hear more? Check out distributed.fmConnect 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 beyondHow Obie and Shopify use AIReflections on pair programming and the future of software developmentIn 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 programmingReferences:Patterns of Application Development Using AIShopify CEO Tobi Lutke's now infamous AI memoWhere to connect further:Connect with Obie Fernandez on Instagram and obiefernandez.comFollow TupleWant to hear more? Check out distributed.fmConnect 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 iOSHow Raycast leverages community over dataWhat it takes to sustain Raycast’s biweekly shipping cadence and How dogfooding drives product polish and reliabilityIn 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 UXWhere to connect further:Connect with Thomas Paul Mann on XFollow Raycast on X or join the Slack communityFollow TupleWant to hear more? Check out distributed.fmConnect with Jack Hannah

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 hopeReferencesSwarm Programming with the Swarm BoardClean Code by Robert C. MartinWhere to connect further:Connect with Tim Ottinger on LinkedIn and on his websiteConnect with Industrial LogicFollow TupleWant to hear more? Check out distributed.fmConnect with Jack Hannah

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

Engineering teams whose work leaves an impact thrive on trust, collaboration, and the appropriate technical practices.In this episode of the Distributed podcast, host Jack Hannah sits down with Ryan Bergman, Principal Engineer at John Deere, to explore the impact of Extreme Programming (XP) and agile practices on software development. Ryan shares how XP principles helped stabilize a struggling startup, why pair programming is essential for team cohesion, and how behavior-driven development (BDD) builds confidence in large-scale systems.They also discuss the challenges of remote collaboration, lessons from scaling software at John Deere, and what it takes to align distributed teams around a shared technical vision.Highlights:Rescuing a struggling startup by embracing Extreme Programming to improve collaboration, code quality, and technical executionStrengthening engineering teams with pair programming and the right balance of structure and flexibilityManaging large-scale software development at John DeereBuilding trust across distributed teams through clear communication, shared technical vision, and an emphasis on psychological safetyUsing Behavior-Driven Development (BDD) to create reliable, well-tested systems that give teams confidence in their softwareIn this episode, we cover:(00:00) – Kicking Things Off with Ryan Bergman(01:10) – Ryan’s Journey: From Graphic Arts to Engineering(03:59) – Discovering XP: How Extreme Programming Saved a Startup(08:09) – Pair Programming and Agile Coaching: Rebuilding from the Ground Up(14:14) – Navigating Large-Scale Systems at John Deere(16:22) – The Power of Trust: Autonomy, Collaboration, and ‘Vampire Rules’(21:37) – Building Strong Engineering Teams Through Open Knowledge Sharing(26:49) – Pair Programming Pitfalls: Fixing What Doesn’t Work(37:11) – Behavior-Driven Development: Creating Confidence in Complex SystemsWhere to connect further:Connect with Ryan Bergman on LinkedIn and check out John DeereFollow TupleWant to hear more? Check out distributed.fmConnect with Jack Hannah

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

How do grassroots efforts drive big changes in the world of remote work?In this episode of the Distributed podcast, Jack Hannah sits down with Mike Bland, Developer Experience Platform Architect at EngFlow, to discuss his journey from Google and Apple to leading remote teams. Mike shares insights from his time running Testing Grouplet at Google, starting the Quality Culture Initiative at Apple, and how those experiences shape his approach to building effective remote teams today. From fostering grassroots initiatives to using intentional communication to build trust, Mike highlights the tools and strategies that enable distributed teams to thrive.Highlights:Lessons from Google’s Testing Grouplet and Apple’s Quality Culture InitiativeThe importance of intentional communication in remote workUsing forums, training, and shared goals to align distributed teamsIn this episode, we cover:(00:00) – Kicking Things Off with Mike Bland(02:30) – What Is Testing Grouplet? A Story of Change at Google(08:55) – Lessons Learned from Apple’s Quality Culture Initiative(16:43) – Building Grassroots Communities to Drive Cultural Change(17:54) – Key Challenges for Scaling Communication at EngFlow(22:36) – Creating Effective Synchronous and Asynchronous Touchpoints(30:52) – Using Code Reviews to Build Trust in Distributed Teams(37:11) – Balancing Autonomy and Collaboration for Engineers(45:19) – Final Takeaway: Communication and Remote WorkResources:The Rainbow of Death: https://mike-bland.com/the-rainbow-of-deathEssentialism by Greg McKeown: https://gregmckeown.com/books/essentialism/Grouplets: https://mike-bland.com/2011/09/20/grouplets.htmlWhere to connect further:Connect with Mike Bland on LinkedIn and his websiteMore about EngFlowFollow TupleWant to hear more? Check out distributed.fmConnect with Jack Hannah

What makes hybrid and remote teams successful? In this episode of the Distributed podcast, Jack Hannah sits down with Rachel Trana, Senior Engineering Manager at Grainger, to explore strategies for thriving in flexible work environments. Rachel shares how practices like pair programming, effective status updates, and intentional onboarding can help teams stay aligned and productive. She also talks about the unique challenges of fostering communication and connection in a hybrid setup, offering practical advice for leaders and team members alike.If you’re navigating hybrid or remote work and looking for ways to make teamwork seamless, this conversation is full of tips and insights to take back to your team.Highlights:How to create effective kickoffs for hybrid and remote teamsWhy pair programming is a core practice for sharing context and building communication skillsThe importance of clear, concise status updates in daily workflowsStrategies for improving onboarding processes in evolving work environmentsIn this episode, we cover:(00:00) – Kicking Things Off with Rachel Trana(02:30) – Grainger’s Flexible Hybrid Work Approach(04:11) – The Importance of Kickoffs and Context in Team Success(08:36) – How Pair Programming Builds Communication and Technical Skills(16:22) – A Story of Success: Effective Pairing in Complex Projects(17:34) – The Role of Status Updates in Keeping Teams Aligned(22:04) – Rethinking Onboarding for Hybrid Teams(26:32) – Lessons Learned from a Heavy-Handed Approach to Process Change(31:47) – Navigating the Challenges of Isolation in Hybrid Work(33:55) – Final Takeaway: Alignment and CommunicationResources:Connect with Rachel Trana on LinkedIn More about GraingerFollow TupleWant to hear more? Check out distributed.fmConnect with Jack Hannah

What does it take to build high-performing remote teams in a distributed world? In this episode of the Distributed podcast, host Jack Hannah chats with Carlos Rosão, Director of Software Engineering at NewStore, to uncover the strategies that make remote engineering teams thrive. Carlos shares how NewStore fosters autonomy, balances standardization with flexibility, and uses pair programming to reduce miscommunication and encourage collaboration. From prioritizing customer needs to scaling engineering practices across distributed teams, this episode offers insights for leaders and team members navigating remote work.Highlights:The balance between empowering teams and standardizing best practicesHow NewStore uses pair programming and rotation to prevent silos and enhance collaborationWhy in-person meetups still matter for distributed teamsPractical tips for improving communication and ownership in remote settingsIn this episode, we cover:(00:00) – Kicking Things Off with Carlos Rosão(05:16) – NewStore’s Approach to Distributed Work and Time Zone Collaboration(07:04) – Building Trust and Fostering Connections in Remote Teams(11:05) – Balancing Autonomy and Alignment in Team Decision-Making(19:15) – The Role of In-Person Gatherings for Onboarding and Team Cohesion(24:22) – How Customer Feedback Drives Product Innovation at NewStore(36:23) – Final Takeaway: Scaling Distributed Teams and Fostering High PerformanceWhere to connect further:Connect with Carlos Rosão on LinkedInVisit Tales of Engineering LeadershipMore about NewStoreFollow TupleWant to hear more? Check out distributed.fmConnect with Jack Hannah

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

How does human connection shape the way we build software?In this episode of the Distributed podcast, host Jack Hannah talks with Dave Farley, renowned software engineer, author, and expert in modern software development. Dave shares insights from his 40-year career, covering everything from extreme programming to the role of AI in software engineering. He explains why pair programming is one of the most underrated practices and how fostering trust in remote teams leads to better collaboration and creativity.Dave also explores the trade-offs of remote and hybrid work, the importance of high-quality engineering practices, and why continuous delivery remains essential for building world-class software.Highlights:Why software development is a team game and not a solo endeavorHow pair programming boosts productivity and code qualityLessons from ThoughtWorks on scaling extreme programming with large teamsThe evolving impact of AI on software engineering How remote teams can not only build trust but maintain itIn this episode, we cover:(00:00) – Kicking Things Off with Dave Farley(01:33) – Dave Farley’s Path From Early Computing to Today(05:42) – Leading a Distributed Team: First Remote Experience(07:58) – Solving Remote Work Challenges Through Human Connection(11:46) – Building Trust: The Key to Strong Software Teams(15:55) – Pair Programming: The Secret to Better Collaboration(18:55) – Overcoming Resistance to Pair Programming in Teams(28:35) – How AI Is Changing Software Development Forever(36:29) – Test-Driven Development as the Future of AI Coding(40:06) – The Biggest Challenge of Remote Work: New Teams(43:14) – Finding the Right Balance Between Remote and OfficeWhere to connect further:Connect with Dave Farley on LinkedIn and his websiteFollow TupleWant to hear more? Check out distributed.fmConnect with Jack Hannah

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 [email protected] 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

How do you maintain a balance between deep work and collaboration in a remote-first world? In this episode of the Distributed podcast, Host Jack Hannah sits down with Blake Irvin, Observability Engineering Lead at SumUp, for his insights into how developers and teams thrive remotely. Blake shares how SumUp approaches distributed work, the importance of clear communication, and why protecting focus time is critical. From balancing asynchronous and synchronous collaboration to using tools like Honeycomb, Incident.io, and Tuple, Blake offers a practical look at what makes remote teamwork successful.Highlights:Reducing friction - how to choose between synchronous and asynchronous communication Why meaningful connections during work hours can transform team dynamicsBlake’s strategies to protect focus and unlock deeper, more meaningful workHow the right tools can create a culture of seamless collaboration even in distributed environmentsIn this episode, we cover:(00:00) – Kicking Things Off With Blake Irvin(01:10) – The Role of Observability in Remote Engineering(04:48) – What a Healthy Remote Work Culture Looks Like(08:23) – Rethinking Urgency in Team Communication(12:58) – Collaboration Tools That Make Remote Work Easier(18:02) – Why Pairing is Essential for High-Performing Teams(22:10) – Async vs. Sync: When to Use Each for Maximum Impact(27:48) – How In-Person Connection Strengthens Remote Teams(32:49) – Lessons from Scaling a Startup to Millions of Users(37:04) – The Power of Experimentation in TeamworkReferenced:37signals blog post: Group Chat: The Best Way to Totally Stress Out Your TeamPaul Graham’s essay: Maker’s Schedule, Manager’s ScheduleHoneycomb.io for distributed tracingIncident.io for collaborating on incident responseTuple’s Pair Programming GuideWhere to connect further:Connect with Blake Irvin on LinkedIn and GitHubMore about SumUpFollow @tupleWant to hear more? Check out distributed.fmConnect with Jack Hannah

How do soft skills shape success in a remote-first world?In this episode of the Distributed podcast, Host Jack Hannah chats with Callie Buruchara, Senior Software Engineer at Uplift Agency, to explore how mastering communication and emotional intelligence (particularly in a remote work setting) can transform your career. Callie shares her journey from high school English teacher to software engineer and how her people-first approach became her superpower. Plus, hear Callie’s take on balancing deep work, managing expectations, and why some of the toughest lessons often come from unexpected places.Highlights:Navigating remote work dynamics and adapting to different communication styles to foster collaboration and reduce misunderstandingsThe power of emotional intelligence in building trust and resolving conflict within distributed teamsCallie’s strategies for balancing prioritization, managing time effectively, and protecting mental healthWhy addressing friction early and practicing honest communication strengthens team dynamicsHow soft skills, like empathy and vulnerability, often play a pivotal role in technical successIn this episode, we cover:(00:00) – Kicking Things Off with Callie Buruchara(01:12) – Why Soft Skills Define the Majority of Work(03:27) – The Real Challenge in Tech: It’s Not JavaScript, It’s People(08:06) – How to Navigate Conflicting Communication Styles at Work(12:16) – Managing Priorities in a Remote Setting Without Explicit Cues(17:59) – Handling Workplace Conflict: Say Something Before Anger Takes Over(22:23) – When Ignoring Friction Backfires: A Story of Team Breakdown(28:33) – The Hidden Struggles of Remote Work: Loneliness and Lost Signals(33:46) – The Feedback Litmus Test: How to Grow in Communication Skills(39:54) – The Hardest Part of Remote Work: Recreating SpontaneityWhere to connect further:Connect with Callie Buruchara on LinkedIn and her WebsiteEmail Callie at [email protected] More about Uplift Agency Ltd. More about firstpromo.devFollow @tuple

How do great teams build better software? In this episode of the Distributed podcast, host Jack Hannah speaks with Josh Kerievsky, founder and CEO of Industrial Logic and one of the earliest pioneers of Agile software development. Josh shares insights into the practices that help teams thrive, including sufficient design, pairing, ensembling, and continuous deployment. He also advocates for a balance between in-person and remote collaboration, the evolving role of AI in software development, and why a focused approach is what matters most for success. Highlights:The concept of sufficient design and why perfection isn’t always necessaryHow pairing and ensemble programming improve knowledge transfer and help develop stronger teamsThe role of continuous deployment in elevating software delivery practicesBalancing in-person and remote collaboration to support team mental healthThe potential and challenges of AI in software developmentIn this episode, we cover:(00:00) – Kicking Things Off With Josh Kerievsky(01:05) – When Agile Clicked: Lessons From the 90s(05:05) – Sufficient Design: Knowing When Good Enough Is Enough(09:50) – Remote, Hybrid, and In-Person Work: Finding the Right Balance(12:27) – Social Programming: Why Pairing and Ensembling Matter(20:43) – The Making of a High-Performing Software Team(30:11) – AI, Specification-Driven Development, and the Future of Coding(33:46) – Josh’s Advice: Collaborate More, Code BetterReferenced:Agile Manifesto: https://agilemanifesto.org/Where to connect further:Connect with Josh Kerievsky on LinkedInMore about Industrial LogicFollow @tupleWant to hear more? Check out distributed.fmConnect with Jack Hannah

Remote work isn’t just a shift in where we work… It's changing how we work. The Distributed podcast, from Tuple, focuses on the realities of remote software development, unpacking the tools, strategies, and mindsets that help teams thrive in a distributed world.In this trailer, host Jack Hannah sets the stage for what’s ahead: candid conversations with engineers and leaders navigating the complexities of remote work, sharing their stories, and offering actionable insights to help you and your team succeed. From balancing focus to building strong team dynamics, this podcast is here to help you make the most of remote work.Hear how some of the brightest minds in tech are solving remote challenges. Listen and subscribe to the Distributed podcast wherever you get your podcasts.