Optimizing remote work: Pull Requests, Stand-ups, and emojis with Kasey Kelly
summary
Clear, concise communication is the claim and the practice: enforce PRs with QA steps and links, use GitHub Actions + Town Crier changelog gating to auto-create releases, favor biweekly demos and short Loom demos under 2 minutes, track time with Harvest, and tie Jira, Teams, Slack, Notion and Basecamp so breadcrumbs follow. Meetings sit every two weeks, some collaborators have about four hours overlap per week across time zones. The pipeline reduces surprise invoices, unanswered PRs, and makes status reports quick and trustworthy.
AI-written summary · about
chapters (7)
- 0:00Remote work intro
- 3:34Setting expectations
- 8:28Meeting cadence efficiency
- 15:54Sprints and async work
- 20:53Daily collaboration tools
- 27:57Point releases status
- 36:45Q&A responsiveness
related talks
21mWorking across timezones tips and tricks
37mThe Effective Remote Developer
43mOut of Sight, Out of Mind: Survival tricks and tools for remote developers
25mDeveloper Joy – How great teams get s%*t done
43mKeynote: Coding Culture
52mConfronting Common Productivity Hurdles in Modern Software Development
28mPull Requests: Merging good practices into your project
36mDistributed & Local: Getting the Best of Both Worlds