Skip to content

Move the Saga up, give it 30 minutes, make Heartbeats a Stretch Workshop - #8

Open
nadvolod wants to merge 4 commits into
sync-java-essentials-with-tsfrom
saga-up-heartbeats-stretch
Open

nadvolod wants to merge 4 commits into
sync-java-essentials-with-tsfrom
saga-up-heartbeats-stretch

Conversation

@nadvolod

Copy link
Copy Markdown
Collaborator

Stacked on #7, which it needs for the single invite link and CopyLink. Merge #7 first.

Learners rate the Saga lab the most useful of the day, so it moves up and gets more time. Heartbeats gives up its slot.

Changes

  • Order: the Saga section (17-saga-01 to 07) and its lab now run straight after the Quiz, ahead of Child Workflows, Continue-As-New and Heartbeats. The agenda (themeConfig.toc) and the Advanced divider's subtitle follow the new order.
  • Saga lab: 25 → 30 min. The Track's own limit is still 40.
  • Labs block: 35 → 25 min. Child Workflows (15 min) and Continue-As-New (10 min) are core. Heartbeats is now a Stretch Workshop: both lab slides offer it to people who finish early. Its slides are still taught to everyone.
  • CONTEXT.md: new term, Stretch Workshop. It describes live delivery only: the Workshop, its Track and its README row don't change.
  • ADR 0005: records the decision and the options we rejected.
  • 14-child-workflows.md: its mention of the Saga section now points back to it instead of forward.

The day comes out 5 min shorter, and that 5 min stays as buffer.

Not in this PR

  • The Python and TypeScript DevDays repos need the same reorder and Stretch change made separately.

Verification

  • slidev build succeeds.
  • SlidesMatchTest, SlidesParseTest and WalkthroughsTest pass.
  • verify-content.sh and check-readme-index.sh pass.

🤖 Generated with Claude Code

nadvolod and others added 4 commits November 14, 2026 13:18
- The Saga section and its lab run straight after the Quiz, ahead of
  Child Workflows, Continue-As-New and Heartbeats; the agenda follows.
- Saga lab: 25 -> 30 minutes.
- Labs block: Child Workflows and Continue-As-New core (25 minutes);
  Heartbeats offered to early finishers on both lab slides. Its slides
  are still taught to everyone.
- CONTEXT.md: new term, Stretch Workshop (live delivery only).
- ADR 0005 records the decision and the options rejected.
- Child Workflows notes: the Saga reference now points back.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
A question slide after "What is Continue-As-New?": the room answers, then
two clicks reveal that only your code knows what state to carry forward, and
the three reasons (history is the state, it needs a safe point, most
Workflows never need it), explained in the speaker notes.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
The second reason on the question slide becomes "It needs cleanup first":
finish handlers, drain buffered Signals, settle pending Activities and Child
Workflows, and release anything held outside Temporal.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
A diagram slide after "What is Continue-As-New?": run 1's history nears
the limit, it continues as new handing over only cyclesCompleted, and each
new run starts with a fresh history under the same Workflow ID.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant