0 views collected around this technical thread.
This article explains the differences between remote and distributed software teams, outlines the advantages of a distributed model, and provides practical strategies, tools, and communication techniques for effectively coordinating and leading large, multi‑location development projects.
This article explains the differences between remote and distributed teams, outlines the benefits of a distributed model, and provides practical tips, communication strategies, meeting structures, video documentation methods, and team‑management practices for successfully running a distributed software development project.
This article examines the difficulties faced by distributed agile teams—including limited participation, high communication costs, business coupling, practice inconsistencies, and cross‑site dependencies—and outlines concrete strategies such as local team formation, clear agreements, refined processes, and coordination mechanisms that improve collaboration and delivery efficiency.
The article shares practical experiences and advice from Ant Financial and a startup founder on why remote work should be adopted, how to overcome communication and productivity challenges, and key management practices that foster autonomy, competence, and belonging in distributed engineering teams.
The talk outlines how Tetrate.io’s globally distributed teams overcome time‑zone, communication, and tracking challenges by using transparent calendars, concise asynchronous meetings, clear email and Slack etiquette, fine‑grained task ownership, open‑source style visibility, and occasional face‑to‑face interactions to boost efficiency and collaboration.
This article shares Tubi Beijing's extensive remote‑working experience, comparing communication challenges to distributed system problems and offering practical strategies—such as asynchronous messaging, task‑queue management, regular cross‑site visits, and collaborative tools—to improve trust, efficiency, and team cohesion across time zones.