Diagrams
Structure gets a diagram. Explain picks the kind that matches the relationship being shown:
- Flowcharts for branching logic and architecture: the check that can fail, the cache hit versus the miss, the loop back
- Sequence diagrams for parties exchanging messages: browser to server to database, request and response, handshakes
- State diagrams for one thing moving through named states: a connection, a request lifecycle, a UI mode
The narration walks the diagram in order, with the pointer landing on each node, arrow, and label as it's mentioned. A decision branch gets explained at the branch, not in a paragraph three slides later.
A diagram shows structure that holds still. When the point is movement through that structure, the lesson reaches for an animation instead, and for the source behind it, a code slide.
Getting good diagram slides
Mention the flow you care about: with a diagram of the request flow or show the states a connection goes through steers the explainer toward the right picture.