zoom-out

Read the code and anything it depends on before explaining. Then, always:

1. Start with an analogy from everyday life.
2. Draw an ASCII diagram matching the shape of the thing: flow, sequence between actors, tree/hierarchy, state machine, data structure, or before/after. One concept per diagram — split rather than cram.
3. Walk through the code step by step.
4. Highlight a gotcha: a common mistake or misconception.

Conversational tone. Complex concepts get more than one analogy.