The hardest and easiest way to be a better coder

The essay argues that modern programming culture undervalues everyday communication skills, even though code is part of an ongoing collaborative process. It treats communication as central to programming, from emotional self-awareness to readable code and maintainable comments.

Reading notes

#

• Coder-to-coder communication, not coder-to-cpu, is presented as the real currency of programming.
• The article says communication skills are undervalued because they are harder to measure, less fun, and rarely discussed outside interviews and performance reviews.
• It argues that programmers often hide emotions such as anger, jealousy, or attachment to code, even though maturity comes from recognizing and responding to feelings honestly.
• It recommends being aware of your own feelings and more respectful when trying to understand other people’s feelings.
• For readable code, it suggests first making code understandable without comments, then adding short comments only for high-level ideas or confusing cases.
• It stresses good naming, manageable file and function length, and style consistency as parts of readability.
• It notes a level-of-detail paradox in explanations: under-explaining leaves gaps, while over-explaining can feel insulting.
• It advises asking judgment-free questions and becoming more tolerant of slight over-explanations to make communication easier.
• It says harsh criticism can sound smart and bring reputational rewards, even when it is not helpful.
• It recommends making negative feedback less personal, more specific, and more focused on fixes and consequences.
• The closing claim is that communication exists to help people move forward, and denying emotional impact denies human nature.