Hasty Treat - Communication Skillz

Episode Summary

Executive Summary: The episode argues that communication is a critical developer skill that can determine project success, team trust, and client satisfaction as much as coding ability. The hosts discuss why poor communication makes good developers appear ineffective, and offer practical ways to improve through intentional practice, team systems, recurring updates, and choosing the right tools like Slack, GitHub issues, Notion, and email workflow tools.

Main Topics: Why communication matters in development: The hosts stress that communication can make or break a project, affecting deadlines, client trust, team coordination, and how developers are perceived professionally. Intentional practice and habit-building: Improving communication is framed as a deliberate practice, not an accidental skill; developers should create habits like regular updates and asking clarifying questions. Systems and team processes: The episode recommends team-wide systems such as stand-ups, feedback rules, and defined communication norms so everyone knows when and how to share information. Over-communication versus silence: The hosts argue that while over-communication can be annoying, it is often preferable to leaving teammates or clients uninformed about progress or risks. Communication tools and workflow: They compare communication tools by use case: Slack for real-time chat, GitHub issues for work tracking, Notion for planning, and email tools like Missive for shared inbox collaboration. Manager and team-lead balancing act: Scott raises the challenge for developer managers: how to stay informed without micromanaging, while still letting people work effectively.

Key Arguments: Communication skills are as important as technical development skills because they directly affect project outcomes and reputation. A developer can be seen as 'bad' mainly because they are hard to reach, miss deadlines, or fail to communicate—not necessarily because their coding is poor. Teams need communication systems and rules, not just a general expectation that people will 'communicate better.' Intentional routines like weekly client updates or automated Slack notifications can prevent misunderstandings and missed expectations. Over-communicating is usually less harmful than under-communicating because it keeps stakeholders informed and reduces surprises. Different tools should be used for different types of communication: real-time chat, tracked tasks, long-form planning, and shared email collaboration. Managers must balance regular check-ins with giving developers space to execute without constant interruption.

Data Points: Sentry issue count: about 6 or 7 different errors - Scott describes his dashboard for a React application and says he can see several active issues at a high level. Repeated error occurrences: a couple thousand times - One Sentry issue in Scott’s dashboard has occurred many times across users. Affected users: 338 people - Scott notes that the same error has impacted a specific number of users. User-specific error frequency: 0.5% to 80% - He explains that one user may account for a tiny fraction of the error rate while another user may experience it most of the time. Podcast episode reference: episode 75 - The hosts reference a prior episode focused on feedback and criticism. Priority system: P1 through P4 - Wes describes a Todoist-inspired priority scheme used in GitHub issues.

Pivotal Quotes: "communication skills can make or break a project" — Scott: Used to introduce why communication is a core professional skill for developers. "no one can read your mind" — Scott: Explaining why developers must clearly express concerns, progress, and blockers rather than assuming others know. "Over-communicating necessarily isn't a problem" — Scott: Discussing why frequent updates are often better than leaving teammates or clients in the dark.

Implications: Developers who communicate clearly and consistently are more likely to keep projects on track, build trust, and avoid avoidable conflict. Teams should define communication habits and tools intentionally, especially as they scale.