Tips for Communicating

Episode Summary

Executive Summary: The episode is a practical guide to better professional communication, covering email, code reviews, meetings, and Zoom etiquette. Scott and Wes emphasize clarity, brevity, friendliness, and respect for others' time, then reinforce the advice with audience-submitted tips. The discussion also includes tools like Calendly/SavvyCal, Loom/private video sharing, and workflow habits that reduce friction and prevent misunderstandings.

Main Topics: Email communication fundamentals: Tips for writing clearer emails: number questions, bold key asks, use paragraphs, avoid awkward dot-by-dot drafting, stay friendly, and give people an out when making a big request. Managing CCs, BCCs, and recipient awareness: They stress being intentional about CCs/BCCs so people are not overloaded or left out of important threads, and highlight how misusing CC can be passive-aggressive or confusing. Code review communication: The hosts focus on asking good questions, avoiding ego-driven feedback, not insulting code or developers, and using objective conventions like linters and formatting tools to reduce subjective conflict. Meetings, in-person conversations, and time respect: Advice includes setting agendas, clarifying expectations, sending follow-up summaries, staying on topic, and being aware that people’s time is valuable and should not be wasted. Video calls and async video sharing: They recommend screen recordings, Loom/private video links, and meeting timelines to clarify complex issues, demonstrate bugs, and reduce back-and-forth. Remote work and asynchronous updates: Audience tips and discussion reinforce over-communicating without verbosity, using scheduling tools, and sharing updates in formats that reduce interruption while keeping others informed. Tools and sponsor mentions tied to workflow: Throughout the episode they reference Sentry, Sanity, and Auth0 as examples of tools that support reliability, structured content workflows, and authentication with less friction.

Key Arguments: Clear structure makes communication easier to parse: numbered lists, bullets, and paragraphs help busy people respond accurately. Bolded asks help the recipient immediately identify what action is being requested, especially in cold emails. Tone matters; being technically correct but terse can make bad news feel harsher than intended. When requesting a favor or a big exception, you should explicitly acknowledge it is a big ask and offer an easy out. CCs and BCCs should be used sparingly and intentionally because every added recipient creates cognitive load and potential social friction. Code reviews should prioritize curiosity and shared problem-solving over judgment, and objective tooling like Prettier and ESLint reduces conflict. Meetings should have agendas, timing, and clear action items; otherwise they become time-wasting ambiguity. Screen recordings and async audio/video can explain context faster than text alone and are especially helpful for support, training, and bug reports. Good communication in remote settings requires being succinct without being vague, and being aware of time zones, statuses, and personal boundaries. Audience-submitted tips largely reinforced the hosts’ core thesis: concise, friendly, specific communication improves outcomes.

Data Points: Episode structure: 4 major communication sections plus Twitter tips - The hosts organize the show into email, code reviews, in-person conversations, Zoom/video calls, and then audience-submitted advice. Free trial offer: 2 months free - Sentry promotion mentions coupon code TASTYTREAT for two free months. Sponsor incentive: Double the free usage share - Sanity promotion offers increased free usage share via syntax.io/sanity. Podcasting schedule: 6-7 openings every Monday - They describe reserving recurring weekly podcast interview slots using a scheduling tool. Audio speed preference: 2x - Wes notes that he often listens to audio at double speed, especially for internal or informational content. Household / workflow example: 3 room sensors - Scott discusses buying an Ecobee package that included three room sensors on the used market. Course discount: $10 off - Wes plugs courses with coupon code SYNTAX for ten dollars off. Audience or channel size: 342,000 subscribers - Wes mentions his YouTube channel’s subscriber count while plugging his UI/build series.

Pivotal Quotes: "number your asks" — Wes Boss: Core email advice: make multiple requests easy to scan and answer. "be cognizant of who's being CC'd on what" — Scott Tolinsky: Advice about minimizing inbox overload and respecting the relevance of recipients. "don't insult the code" — Wes Boss: Code review guidance emphasizing respectful, non-personal feedback.

Implications: The episode argues that strong communication is a technical skill: it improves collaboration, reduces rework, and lowers social friction. For developers and teams, adopting clearer structure, objective tooling, and better async habits can make work faster and more humane.