A Branch in Time (a story about revision histories)
summary
A concrete claim: revision history quality determines maintainability. Examples include using git blame and git log -S to trace why a memory sort existed, digging up a pull request or tracker link, and using interactive rebase plus amend and force-with-lease to rewrite messy commits. Advice shows exact commands, staging strategies (patch, fixup), what to write in commit messages, when to prefer git annotate over blame, and how to keep histories searchable and useful.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:15Meet SEMA
- 7:02Meet Josie
- 13:44Finding the revision
- 14:40Maintaining the code
- 18:38Commit messages
- 19:28Mind hacks
- 21:27Shape your commits
- 23:46Use git history
- 25:25Outro
