Rapport, humor, and being human at work

People decide how hard to listen to you long before you present the evidence, and that pre-decision is built from a hundred tiny interactions this book has so far treated as filler: how you greet, whether you remember their launch, whether working with you is pleasant. This chapter takes the human layer seriously as a skill: rapport as accumulated deposits, humor with a safety model, and the professional version of being yourself.

The warmth and competence axes

Decades of social research and all of engineering folklore agree on the same two-axis map: people read others on competence (can they do the thing?) and warmth (are they on my side?). Engineers optimize the first axis and treat the second as noise, but the combination is what determines outcomes: competent-and-cold reads as a threat (technically right, and somehow every review with them is exhausting), warm-and-incompetent as a liability, and warm-and-competent as the person whose pushback gets heard as help. Nothing in this chapter trades competence away; warmth is additive, and it is mostly made of cheap, specific acts.

Rapport is a ledger of small deposits

Not charisma: bookkeeping. The deposits:

  • Names, used and spelled right (Chapter 1), and pronounced right; asking "am I saying Nguyen correctly?" once is itself a deposit.
  • Remembering stated facts and following up. "How did the marathon go?" three weeks later is worth fifty generic greetings. Keeping light notes ("Ines: marathon Oct; Sam: new puppy") is not creepy; it is what caring looks like at scale, restricted to things people told you themselves.
  • Noticing work while it is in progress: "I saw the refactor land; that migration path was clean" costs ten seconds and is rarer than formal praise (Chapter 2).
  • Micro-generosity: the link they needed, the intro ("you two are solving the same problem; connecting you"), the meeting summary nobody asked for (Chapter 9), warning someone before a surprise (Chapter 3's heads-up culture).
  • Responding to bids. When someone shares news, a joke, or a frustration, the small acknowledgment ("ha!", "congrats!", "ugh, that pipeline again?") is the deposit; silence is a small withdrawal. Chat makes this nearly free: one emoji reaction.

Withdrawals are larger than deposits (one public dismissal undoes months), which is the accounting reason behind Chapter 5's private-first rule.

A safety model for humor

Humor at work is high-return and has sharp edges, so treat it like any dangerous tool: know the safe operating envelope.

Safe by default (punches at situations or shared conditions):

  • The shared absurdity: build systems, naming things, timezone arithmetic, the demo gods (Chapter 10), "it works on my machine" as a genre.
  • Mild self-deprecation: "I've been personally victimized by this YAML file." Signals confidence, in moderation.
  • The callback: referencing the team's own running jokes ("queue goblin strikes again") builds belonging; every healthy team has a small mythology, and contributing to it is membership.

Handle with care:

  • Teasing individuals: requires an established relationship, even footing, and a topic they themselves joke about; when in doubt, down, not across, never at juniors.
  • Irony and sarcasm in writing: dead on arrival across cultures and text (Chapter 17); the /s tag (Chapter 15) is a patch, not a license.
  • Humor during someone else's incident or failure: their call to joke about it, not yours; the postmortem gets funny only after the person at the center laughs first.

Off the table: anything that punches down (role, seniority, accent, background), appearance, identity, and the small-talk avoid column. No exceptional funniness rescues these; the room's laughter and the room's opinion of you are separate ledgers.

The self-deprecation budget deserves its own line: occasional self-mockery reads as confidence, but a steady drip ("I'm probably wrong as usual, but...") is status leakage that quietly undermines the promotion case you are building in Chapter 19. Joke about your YAML luck, not your competence.

Don't be confused: friendly and friends are different contracts. You owe every colleague friendliness: warmth, good faith, small talk, remembering their marathon. You do not owe anyone friendship: weekends, secrets, drinks, emotional labor. Most workplace social discomfort is a boundary confusion between the two, and the graceful decline keeps the first while declining the second: "I'm going to skip the bar, but I'll absolutely be at lunch tomorrow." Warm on the relationship, clear on the limit, zero apology inflation (Chapter 20).

Being human in the ordinary hours

The moves that make "how are you?" less of a protocol and more of a relationship, without oversharing:

  • The honest-lite status: "Running on coffee; launch week. You?" gives one true detail and returns the ball. Compare the two failure modes: "fine" (wall) and the unabridged medical history (flood).
  • Admitting difficulty in moderation: "This migration is kicking me today" normalizes struggle, invites help (Chapter 3), and costs nothing when said by someone whose competence is established; juniors earn the same right by pairing it with a plan ("...so I'm timeboxing to lunch and then asking Sam").
  • Sharing wins without the humble-brag contortion: "The cap shipped and the graphs are gorgeous; extremely pleased with myself today" is honest joy and rooms like it; "so humbled to announce..." is neither humble nor announcement.
  • Celebrating others loudly and often (Chapter 2, Chapter 20); the person who reliably amplifies teammates' wins acquires a strange property: everyone wants them in the room.

Remote teams need all of this on purpose: the two minutes before the agenda, reacting to news in channels, the optional coffee chat. Distributed warmth is scheduled warmth, and scheduling it does not make it fake; it makes it survive the timezone math.

👉 Rapport is the human layer working with you; the last skills chapter is for when the humans get complicated: office politics as a legitimate engineering discipline, boundaries that hold without drama, and the field guide to difficult colleagues, each with a script. On to Chapter 28.