The social layer: joining, leaving, and everything human

Around the work sits a layer of small human genres: introductions, congratulations, goodbyes, condolences, sick days, vacations. Each is short, each has conventions, and each is memorable out of proportion to its length; people forget your standups and remember your farewell message. This chapter is the phrasebook for the moments that are about people, not systems.

Joining a team

The self-introduction message, posted in the team channel in week one:

Hi all o/  I'm Alex, joining the platform team today from FinCo, where
I mostly did payments infrastructure. I'll be picking up the queue
workstream with Sam. Currently drinking from the firehose, so expect
basic questions for a few weeks; pointers to docs I should have read
are very welcome. In person I'm in the Lisbon office, usually 9 to 5
WEST.

The anatomy: name, where from (one clause), what you will work on, an explicit license for your own beginner questions, and logistics. The beginner-questions line is doing real work: it pre-frames a month of "where does X live?" as expected rather than worrying. Use the license while it lasts; the new-joiner card quietly expires after a quarter, and the asking chapter's show-your-work rules take over.

The receiving side takes one line and is worth it every time: "Welcome Alex! I own the deploy tooling; ping me any time, no question too basic." Teams where every joiner gets three of those messages onboard measurably faster, and it costs ten seconds.

Congratulations

Specific beats generic here exactly as in Chapter 2; "congrats!" is a reaction emoji in word form, while one detail makes it a message:

• Promotion: "Congrats, very well deserved. The INC-214 response alone was a senior-engineer performance."
• Launch: "Congrats on shipping! The migration path especially was clean work."
• New baby: "Congratulations! Enjoy the leave and ignore this channel completely; we've got it." (The second clause is the gift.)
• Leaving for a new job: "Congrats on the new role; their gain, our loss. Thanks for everything on the queue work." Never guilt-trip a leaver, and never speak of their new employer with resentment.

Farewells

Your own leaving message is read by everyone and remembered; the genre rules are strict because the failure modes are famous. Gratitude, specifics, contact info, zero grievances:

Friday is my last day after four years. Highlights I'll carry with me:
the 2024 rewrite (still the best team I've worked on), and watching
the platform go from two nines to four. Thanks especially to Sam, who
taught me what a good design review feels like, and to this channel
for answering five hundred of my questions. I'm at alex@... and on
LinkedIn; if you're ever near Lisbon, coffee is on me. Keep the DLQ
drained o7

Whatever the real reasons for leaving, the farewell message is not the venue; the exit interview is. A bitter goodbye buys ten seconds of satisfaction and a permanent last impression, and the industry is small.

When a teammate is laid off (as opposed to leaving), the register changes: no public celebration of their "next chapter" they did not choose. Reach out privately, concretely: "I'm so sorry. I'd be glad to be a reference, and I know two teams hiring for exactly your profile; want intros?" Offers of specific help land; "let me know if you need anything" politely evaporates.

Condolences and hard news

When a colleague loses someone or faces serious illness, the rules are: short, warm, zero questions, zero pressure to reply, and concrete cover for their work:

• "I'm so sorry, Maria. No need to reply to this. Your on-call is covered and the review can wait; take whatever time you need."
• On their return, follow their lead: "Good to have you back" and normal work talk unless they open the topic.

Never ask for details of an illness or absence; "take care of yourself, we've got it covered" is complete. The manager may need specifics; you do not.

Sick days, time off, and handovers

The sick-day message owes exactly two things, availability and coverage, and zero medical detail:

Out sick today, hopefully back tomorrow. Nothing of mine blocks
anyone; the #4132 review can go to Ravi if it gets urgent. I'll be
off Slack.

("I'll be off Slack" is a boundary sentence, and teams with healthy norms respect it; do not write "available if needed" unless you mean it.)

Planned time off has two moves. The early flag, weeks out: "Planning to be out July 3 to 14; flagging now so the release plan can route around it." And the handover note the day before, which is a runbook for your absence:

OOO July 3-14, back the 15th. Handover:
- Queue migration: 60% done, paused safely; nothing runs while I'm out.
  State doc: go/queue-mig. Sam has context if platform asks.
- On-call: swapped with Ravi (thanks Ravi).
- Decisions that can't wait: Dana can make any call on the migration;
  bias to "pause" over "improvise".
- Everything else keeps until the 15th.

The matching OOO auto-reply is three lines: dates, who covers what, when a reply can be expected. "I will respond to your email upon my return" beats promising to check mail on a beach, and then actually not checking it; a boundary stated is a boundary others can plan around.

Don't be confused: PTO is the accounting unit (paid days off, covering vacation and often sickness); OOO is the state of being unavailable, whatever the reason; leave is the word for the long structured absences (parental leave, medical leave, sabbatical). "I'm on PTO Friday" and "I'm OOO Friday" both work for a day off, but someone "on leave" is gone for weeks or months and should be dropped from day-to-day threads entirely, not cc'd "just in case".

The small apology

Not the incident kind (Chapter 10); the human kind, for the day you were short with someone:

• "Hey, I was curt with you in standup; the deadline is not your fault and I'm sorry. Your question was legitimate; here's the real answer."

Anatomy: name the behavior plainly, no "sorry if you felt", no excuse riding in the same sentence, and repair (the real answer) attached. It takes thirty seconds, and it is one of the strongest seniority signals in this book precisely because it is rare.

Small talk: the map

Small talk is protocol, not content (Chapter 1), and the skill is topic selection plus graceful exit:

Cross-cultural note: the amount of expected small talk varies hugely (two exchanges in Berlin, ten in Austin, and in much of Asia the relationship-building is the meeting). Match the room. Exiting gracefully: "I'll let you get to it; good luck with the launch" or, in a call, the host's "alright, let's dive in" ends the phase for everyone.

Opting out of social events is allowed and needs one line, no excuse inflation: "I'll skip the karaoke but see everyone at dinner." Nobody professional keeps score of your evenings, and "I don't drink, I'll have a coke" requires no elaboration in any healthy workplace.

👉 Everything so far assumed engineers talking to engineers. The next chapter crosses the aisle: product managers, designers, support, sales, and customers, where the same facts need different words and the translation itself is the skill. On to Chapter 20.