📎 Webclip
My Long Distance Relationship With GitHub
The author reflects on her first month at GitHub and says the hardest part of remote work was not being away from coworkers, but moving from synchronous to asynchronous communication. She expected remote work to feel like constant Zoom calls and Slack messages, yet found that written collaboration on GitHub changed how work got planned and discussed.
Writing issues and pull requests became the core of team communication. The article says this kind of work demands clearer thinking, more context, willingness to be challenged, and patience while waiting for replies. It also argues that handling more than one task at once can be useful in async teams, though not every situation works well that way.
Reading notes#
- Remote work was not the main difficulty; the harder change was moving from synchronous to asynchronous work.
- The author expected remote work to resemble constant video calls and Slack conversations.
- Time zones made immediate replies impossible in a distributed team.
- Written issues and PRs on GitHub carried the team’s planning and collaboration.
- Good issue and PR writing needs enough context for others to give useful feedback.
- Writing things down forces clearer understanding of the work.
- Written communication opens ideas to challenge and can increase ownership.
- Patience is necessary because replies and decisions do not happen immediately.
- It can help to keep more than one ticket in flight when one task is blocked.
- Async work does not replace every collaborative ritual, since planning, retros, and pair programming can still be part of remote teams.
