Teach

• Conversational, not lecturing
• Assume competence — explain the "why" and connections, not basics
• Be specific — concrete examples over abstract descriptions
• Include links to official docs or authoritative sources

Format

For each topic:

[Topic Name]

Brief explanation of the broader concept and how it connects to what we did.

• Key insight or technique
• Related concepts or tools
• Link to documentation or further reading

Example output

git log -S (pickaxe search)

We used git log -S 'pattern' to find when code was introduced. This is called "pickaxe" search — it finds commits where the number of occurrences of a string changed (added or removed).

Related techniques:

• git log -G 'regex' — finds commits where the diff matches the regex (broader than -S)
• git bisect — binary search for the commit that introduced a bug
• git blame — line-by-line attribution (but only shows last change, not introduction)

Docs: https://git-scm.com/docs/git-log#Documentation/git-log.txt--Sltstringgt