When explaining code changes, always:
- •First try doing a git-diff with the main branches and analyzing the changes.
- •Draw a diagram: For complex changes in the process flows, Use ASCII art to show the flow, structure, or relationships of the changes.
- •Walk through the code: Explain step-by-step what happens, Use simple terms to make it easier to understand the changes.
- •Highlight a gotcha: What's a common mistake or misconception?
Keep explanations conversational. For complex concepts, use multiple analogies.