Week two: pairing, lunches, and both sides of review

Monday through Wednesday of week two. The technical work is converging toward Friday's demo; the communication work this week is mostly human: a harder weekend question, a pairing session with friction, a mixed group lunch with a topic that needs steering, and Alex on both sides of code review pushback in one day.

Monday, 9:10: the weekend question, harder mode

Kitchen again. This time Alex's weekend was genuinely bad, and Noor asks the ritual question.

Noor:  Morning! Good weekend?
Alex:  Honestly, a rough one; our kid ran a fever most of it.
       She's fine now, but we're running on fumes. How was yours?
Noor:  Oh no, glad she's better. Mine was quiet; I finally
       unpacked the last box.
Alex:  The last box! That's the real milestone. OK, coffee, then
       I'm human.

The honest-negative answer, calibrated: true, bounded (one sentence of fact, one of resolution), no medical saga, ball returned, and a light exit line that tells everyone the topic can close. Noor's response is the other half of the skill: brief sympathy, no interrogation ("what fever? how high?"), and moving with the flow Alex set.

If you'd rather not share at all: "Long one; glad to be back in a routine, honestly. Yours?" is a complete answer that closes the door without slamming it. Nobody decent pushes past it.

When the other person shares something hard: "I'm sorry, that sounds exhausting. Anything on your plate this week I can pick up?" Sympathy plus one concrete offer beats extended commentary (Chapter 20's condolence rules, in miniature).

Monday, 9:30: the nothing-to-report standup

Alex:  Short one from me: heads-down on the vault edge cases all
       of yesterday, more of the same today, on track for the
       demo. Nothing needed from anyone.

The invisible-progress day, reported honestly in ten seconds. "Short one from me" is the frame that makes brevity read as discipline instead of disengagement. Resist inflating a quiet day into theater; the team can smell padded standups, and your quiet days buy credibility for the day you talk for ninety seconds because something is genuinely on fire.

Monday, 14:00: pairing, with friction

Alex and Ravi pair on the token fix. Twenty minutes in, Ravi, excited, reaches over and starts typing on Alex's keyboard mid-sentence.

Alex:  (lifting hands off, tone light) Whoa, hostile takeover.
Ravi:  Sorry, it was faster to show.
Alex:  Show away, you have the keyboard now. For next time:
       say "mind if I drive?" and I'll hand it over happily; the
       grab just derails whatever I was mid-thought on.
Ravi:  Fair. ...Mind if I drive?
Alex:  (laughing) Granted.

The boundary, set in real time, with humor as the carrier and the rule stated once, explicitly, for next time (Chapter 23's pairing dialect). Note the order: let the current grab stand (the correction is about the pattern, not the moment), name the cost factually ("derails my mid-thought"), give the replacement behavior. Ravi using it thirty seconds later, as a joke, is the sound of a boundary landing well.

Later in the same session, the reverse skill, admitting lostness:

Ravi:  ...and that's why the epoch pin fixes the replay too.
Alex:  I nodded, but honestly I lost you two steps back, at the
       refresh queue. Thirty-second recap from there?

Tuesday, 12:30: the group lunch

Cafeteria table: Alex, Sam, Ines, Marta, Yuki, and Noor, invited by Alex on the way ("we're doing a table, join us; no agenda, only opinions about the curry"). Three moments from a normal lunch:

Bringing in the quiet one. Yuki has said nothing for ten minutes while the table debates a streaming series.

Alex:  Yuki, you're the one with actual taste here; what are you
       watching these days?
Yuki:  ...promise not to judge? Reality baking shows. All of them.
Marta: FINALLY someone admits it. Which one has the ice cream
       episode?

The invitation, social edition: aimed, low-stakes, and framed as wanting their contribution ("the one with actual taste"), not as charity toward the silent. Then let the table do the rest.

Steering off a hazard. The conversation drifts; someone mentions the election.

Marta: Did you all see the debate last night? I can't believe...
Sam:   (easily) I have opinions I'd need a second beer for, and
       it's Tuesday lunch. Ines, more importantly: settle
       something for us. Is the curry actually spicy or are we
       all weak?
Ines:  You're all weak. In my house this is breakfast.

The redirect: no lecture ("we shouldn't discuss politics"), no freeze; acknowledge lightly, name the mismatch of venue with humor, and hand the table a better toy immediately (Chapter 20's topic map in action). Anyone at the table can do this, not just the senior person, and the whole move takes six seconds.

Family questions, done right. Noor mentions her brother is visiting.

Alex:  Nice; is he the one who does the pottery, or am I
       inventing a sibling for you?
Noor:  No, that's actually him! You remembered that from
       onboarding week?
Alex:  You mentioned the pottery empire; it stuck.

Family talk at work runs on one rule: follow what they have offered, never mine for more. "Is he the pottery one?" builds on volunteered information; "so when are YOU having kids?" excavates, and belongs nowhere. If you remember nothing offered, the safe generic is "any visitors or trips coming up?", which lets them choose the depth.

Tuesday, 15:00: pushback received (his PR)

A comment lands on Alex's PR from Tomas, on the platform team:

Tomas:  blocking: this retries on ANY vault error. Auth failures
        will retry forever and lock the account. Needs an error
        taxonomy before this merges.

Alex:   Good catch on the auth case; that would have been a real
        lockout bug, thank you. Pushed a fix: retry only on
        timeout and 5xx, fail fast on 4xx (a2b91c). On the fuller
        taxonomy: agreed it's needed and it's bigger than this
        PR; opened #781 with your comment quoted. OK to keep that
        part out of this merge?
Tomas:  With 4xx failing fast, yes. Approving.

Receiving pushback in the ideal shape: concede the true core fast and specifically, fix with a commit hash, and split the legitimate-but-larger ask into a tracked follow-up with a clean question (Chapter 7). No defensiveness about the word "blocking"; it earned its label.

Tuesday, 16:30: pushback given (Sam's PR)

Same day, other chair. Sam's PR takes a shortcut Alex thinks is dangerous:

Alex:  question: this reads the tenant ID from the request header
       in the demo path. We removed exactly this pattern in #512
       because header and token can disagree (wrong-tenant risk).
       Is the demo path safe for a reason I'm missing, or did the
       old pattern sneak back in?

Sam:   ...it snuck back in. Copied from an old branch. Fixing.
       Good memory.

Alex:  Only remembered because it scared me the first time. nit
       while you're in there: the TODO on line 40 references the
       dead ticket.

Pushing back on a senior colleague's code: question form first ("is it safe for a reason I'm missing?") because the possibility that they know something you do not is real; evidence attached (#512); zero gloating when it turns out to be a genuine slip. The "only remembered because it scared me" line converts the catch from a status move into a shared war story (Chapter 27).

Don't be confused: pushing back up the seniority ladder and down it use different defaults. Upward or across, lead with the question form and your own uncertainty ("what am I missing?"), because the base rate that the senior person has context you lack is genuinely high. Downward, the same words can read as sarcasm ("is there a reason you did this?" from a senior to a junior lands as a trap), so go plainer and kinder: state the issue, the fix, and one sentence of why, and save the Socratic method for teaching moments you have time to finish. The constant in both directions: the code is the subject, never the coder (Chapter 5).

Wednesday, 11:00: Alex's first lightning talk

Ten minutes at the guild meeting: "What the vault migration taught us about retries." Three moments:

(opening)
Alex:  Show of hands: who has ever retried something into a worse
       problem?... Keep them up if it paged you.... Right, this
       talk is for every hand still up, including mine.

(the unanswerable question)
Tomas: What's the retry budget interaction with the circuit
       breaker?
Alex:  I don't know, and I'd rather not improvise at the front of
       a room. I'll test it this week and post the answer in the
       thread; hold me to that.

(the monologuer)
Guest: (two minutes into a comment with no question mark)
Alex:  I want to do that point justice and we have four minutes;
       can we take it to the thread? If there's a question inside
       it I can answer now, give me the one-sentence version.
Guest: ...fine: do you cap by attempts or by time?
Alex:  Both, and time wins ties. Great question hiding in there.

All three are Chapter 10 run from the speaker's side of the podium: the stake-first opener, the "I don't know" with a delivery date and an invitation to be held to it, and the monologue compressed with respect ("do that point justice") plus a deadline. "Great question hiding in there" forgives the format while rewarding the substance; the guest leaves flattered, not policed.

👉 Two days remain in the sprint: the demo that must not fail, a retro where Alex both gives and takes process criticism, and the 1:1 that closes the two-week loop. On to Chapter 35.