Here,s to history: programming through archaeology
summary
Argues that archaeological methods clarify messy commit histories and demonstrates using git log, git bisect and git blame plus a regression test to locate a permissions bug introduced in 2012, isolate the faulty commits and implement a small fix that resolves the 403/404 mismatch. Claims context and stratigraphy map to commit order and file provenance, shows how a missing artifact (undocumented change) destroys meaning, and treats code as recoverable, improvable history.
AI-written summary · about
chapters (10)
- 0:00Intro
- 1:28Law of Demeter
- 3:03Commit history
- 4:34What is archaeology
- 5:20Human intention
- 9:35Praxis and interpretation
- 12:20Context and stratigraphy
- 16:46context
- 17:27artifact removal
- 21:42conclusion
