Git blame for code comprehension
Summary
This article is a personal exploration of code comprehension and version-control workflows, advocating predictive reading, understanding the evolution of code over time, and using git blame to study a snippet in its historical context. It provides practical workflows and browser/CLI tips for tracing code provenance beyond line-by-line diffs, including local worktrees and shortcuts.