Two weeks in the life: the sprint begins

This part of the book follows one engineer through a full month: first a complete sprint (greetings, standups, glitchy calls, lunches, talks, reviews, ceremonies), then the harder weeks that follow it (a reorg, the bureaucracy machine, a political turf war, and the good week that closes the month), all transcribed and annotated. The cast is the one you know: Alex, our engineer, on the Cart & Checkout platform team; Sam, the senior engineer and Alex's closest friend on the team; Dana, the manager; Priya, the product manager; Ravi and Yuki, teammates; Ines on the neighboring team; Marta in support. This sprint's goals: finish the saved-payment-methods feature and demo it, while the per-tenant queue rollout bakes.

Every scene shows the ideal version and the variations, because the same moment offers many correct sentences and you should own more than one.

Monday, 9:05: weekend talk, both directions

Office kitchen. Alex and Sam arrive at the coffee machine together.

Sam:   Morning! How was the weekend?
Alex:  Really good; we finally did that coastal hike, and I have the
       sunburn to prove it. Yours?
Sam:   Quiet one. Mostly gardening and pretending not to check Slack.
Alex:  The rollout graphs were fine, I checked them so you didn't
       have to. Ready for planning?

What makes it work: one true detail each (hike, gardening), a return question within one breath, and a natural pivot to work when the protocol completes. Weekend talk is a two-line genre; the detail makes it human, the brevity makes it professional.

Other ways to ask: "Good weekend?" (minimal, safe) / "Do anything fun this weekend?" (invites a story) / "How was the long weekend? You were camping, right?" (the gold standard: remembered detail, Chapter 27).

Other ways to answer, by mood: "Great, actually; my sister visited." (positive, one detail) / "Quiet, exactly what I needed." (neutral, complete) / "Honestly, a rough one; the kid had a fever. All fine now though. Yours?" (negative done right: honest, bounded, ball returned) / "Nothing exciting, but I'm caffeinated and optimistic." (deflection with charm, when you don't want to share). The one wrong answer is the seven-minute monologue; the second wrong answer is interrogating someone who clearly gave you a closed door ("quiet one" means move on).

Monday, 9:30: standup, day one

Alex:  Yesterday was Friday, so: rollout held at 50% all weekend,
       error rates flat. Today: starting the saved-payments API,
       aiming to have the schema up for review by tomorrow.
       No blockers.
Ravi:  So I was looking at the token thing, and there's a lot going
       on there, the vault client is kind of a mess honestly, and I
       also had that meeting with the fraud team about the...
Dana:  Ravi, headline version? We can go deep after.
Ravi:  Fair. Headline: token refresh has a bug, I know where, fix
       today. Fraud sync moved to Thursday.

Alex's update is the Chapter 8 shape: outcome, outcome, explicit no-blocker. Dana's "headline version?" is the kind compression every standup needs on tap; note it names the format, not the person's failing.

Variations for "no blockers": "Nothing in my way." / "No blockers; might need Sam's eyes tomorrow, will grab you." (the pre-flag) / "Not blocked, but I'm slower than planned; flagging in case Wednesday looks tight." (the honest amber, Chapter 8).

Monday, 11:00: sprint planning

The team sizes the saved-payments work. Two moments worth stealing:

Priya: The story says "users can save a card." Sizing?
Alex:  Before a number: what does done mean here? Save and reuse in
       checkout, or also manage, as in delete and set-default? Those
       are different sprints.
Priya: ...good catch. Reuse only; management is next sprint. I'll
       split the story.
Sam:   Then I'd say a 5. The risk is the vault integration; Ravi's
       token bug tells me it has sharp edges.
Dana:  One constraint from me: I'm on call this sprint, so plan my
       capacity at half. Better we cut a story now than carry it.

And when Alex thinks a size is wrong:

Ravi:  The audit log piece? That's a 2, easy.
Alex:  Help me see it as a 2; what's driving that? Last time we
       touched audit we lost two days to the retention policy.
Ravi:  ...I forgot the retention part. Call it a 5.

"What does done mean here?" and "what's driving that number?" are the two highest-value planning questions (Chapter 10). Note the challenge shape: not "that's wrong" but "help me see it" plus the evidence (Chapter 6).

Other ways to question an estimate: "What are we assuming goes right?" / "Is that a 2 if the vault behaves, or a 2 including the vault misbehaving?" / "I'd have guessed triple that; one of us knows something. What do you see?"

Monday, 12:30: lunch with a friend

Cafeteria, Alex and Sam. Two minutes in, the conversation turns:

Sam:   Between us, Ravi's rambling is driving me up the wall. Every
       standup is a podcast.
Alex:  Ha, this morning ran long, yeah. To be fair, when he finally
       got to the headline it was a real find; the token bug is
       nasty. Someone could give him the "headline first" trick;
       it changed my standups completely.
Sam:   ...that's fairer than what I said. Maybe I'll pair with him
       on the fix and sneak it in.

This is the venting-versus-gossip line walked correctly: Alex neither joins the character attack ("he IS terrible") nor polices his friend ("we shouldn't talk about colleagues"). He validates the observable fact, adds the counterweight, and steers toward a fix. Friends vent; what you co-sign is up to you.

Don't be confused: venting and gossip are different activities that use the same sentences. Venting is frustration seeking relief, aimed at a situation, discharged and done. Gossip is information seeking an audience, aimed at a person, and it travels. The listener decides which one a conversation becomes: respond to the frustration ("that meeting was rough") and it stays venting; add fuel ("and did you hear what else he did?") and you are now co-authors of gossip that will eventually be quoted with your name attached. The workplace half-life of "just between us" is about a week.

Lunch itself: the rest was the easy kind of talk (Sam's garden, a show Alex is watching, whether the cafeteria curry counts as spicy), which is the point. Lunch with a work friend is where the rapport ledger compounds; it needs no technique beyond showing up and asking one follow-up question about their thing.

Monday, 15:10: the kitchen drive-by, both directions

Alex, walking to the kitchen, passes Ines at her desk:

Alex:  Ines, hey; heads-down or got thirty seconds?
Ines:  Thirty seconds, sure.
Alex:  The export pairing from last sprint: did the format hold up,
       or should I expect a round two?
Ines:  Held up. One nit about date fields; I'll comment on the doc.
Alex:  Perfect, that's all I needed. Back to your queue o/

The drive-by contract: ask permission for the interruption, honor the granted size (thirty seconds means thirty), and close it yourself so they do not have to eject you. "Heads-down or got thirty seconds?" respects that headphones and a full screen are a closed door (Chapter 3).

And the same afternoon, reversed, while Alex is deep in the schema:

Marta: Alex, quick one about a customer ticket?
Alex:  I'm mid-thought on a schema and will lose it; can I find you
       at four? If it's urgent-urgent, tell me and I'll drop this.
Marta: Four is fine, it's not on fire.
Alex:  (at 15:55, walking over) You had a ticket for me?

The deferral that works names a concrete time, offers the urgency override, and is honored to the minute. A "later" that never arrives teaches people to interrupt harder next time; a "four o'clock" that arrives at 15:55 teaches people your door works by appointment.

Variations for deferring: "Give me twenty minutes to land this and I'm all yours." / "Can it go in a message? I'll answer between builds." / "Genuinely can't context-switch right now; is Sam a faster path or should I come find you?"

Tuesday, 9:30: standup, day two, blocked

Alex:  Yesterday: payment schema is up as PR 512. Today: the vault
       integration. Blocked on: schema review; it's small, one
       focused look unblocks everything behind it. Sam, can you?
Sam:   After this meeting. If it's as small as you say, before ten.

Blocked-with-a-name, size stated to make the ask cheap, resolved in the meeting itself. That is the entire purpose of the ritual.

Tuesday, 10:40: the forgotten name, both directions

The new data engineer (introduced at last week's all-hands) waves at Alex in the corridor, and Alex's mind is a blank page.

Alex:  Hey! Good to see you again. I'm so sorry, your name has
       fallen out of my head; I want to get it right.
Noor:  Noor. And you're Alex, right? The queue person.
Alex:  Guilty. Welcome again, Noor; how's week two treating you?

The direct ask, delivered warmly within the first exchanges, costs five seconds of mild embarrassment and buys a correctly used name forever. The alternatives are worse and everyone has used them: weeks of "hey... you!", or the email archaeology mid-conversation. Other recovery routes when you cannot bring yourself to ask: offer your own name first ("Alex, by the way; we met at the all-hands" almost always triggers the reciprocal), ask a third person before walking over, or check the meeting invite or team page (legitimate, do it before the conversation, not visibly during).

And the reverse, minutes later, because symmetry is the theme of this part:

Ines:  Alex, this is... I'm blanking, I'm sorry.
Alex:  Alex. No apology needed, I did the same thing to Noor an
       hour ago.

When someone forgets your name or mangles its pronunciation: zero-cost grace, instant supply of the name, no performance of being wounded. If a mispronunciation persists and you care, correct once, privately, lightly: "Small thing: it's AH-lex, not ah-LEX. I answer to both, but you asked me once to correct you, so." (The same rule you extend to others in Chapter 24.)

Tuesday, 14:00: asking for help, and being asked

Alex has burned his timebox on a vault error. The DM to Yuki, who wrote the original client:

Alex:  Hi Yuki, vault question when you have a moment (not urgent
       before EOD). Goal: exchange a saved-card token during
       checkout. Tried: the flow from your 2024 doc; token exchange
       returns "audience mismatch" (exact error in thread). I've
       ruled out clock skew and the sandbox env var. Am I holding
       the audience field wrong, or has the contract changed since
       the doc?
Yuki:  Ah, it changed in March; audience is now the tenant ID, not
       the service name. Doc is stale, my bad. Updating it now;
       thanks for the nudge.
Alex:  That was it. Thanks! FWIW the rest of the doc held up well.

Anatomy on display: goal, attempt, exact error, ruled-out list, closed question, urgency labeled. Yuki answers in ninety seconds and the stale doc gets fixed for the next person, which is what well-formed questions do: they leave the trail better than they found it.

An hour later Noor asks Alex for help, and Alex is the busy one:

Noor:  Sorry to bother you; do you have time to explain how the
       replay tool works?
Alex:  No bother at all, and yes, but not usefully right now. Two
       options: there's a fifteen-minute walkthrough video from
       the last onboarding (link incoming), or grab me tomorrow
       at ten and we'll run it on a real example together. Honestly,
       do both in that order; you'll get triple the value from the
       live one.

The helpful no-for-now: warmth first ("no bother": kill the apology-debt Noor is carrying as the new person), then routes that actually serve the asker better than an interrupted, distracted yes would have.

👉 Two days in, and the sprint has already used a dozen chapters of this book at conversational speed. Midweek brings the failure modes everyone with a laptop knows: the call where nobody can hear you, the call where you cannot hear them, and the sentence that has to be asked about twice. On to Chapter 33.