Ask Your Code

on YouTube ↗40m

" summary

Argues that asking “why” repeatedly uncovers first principles and shows many version‑control needs are unmet: git covers backups, branching, diffs and archaeology but common, useful questions are hard to answer. Demonstrates exact commands that help — git log two‑dot syntax to see reachable commits, git blame -w -C -C -C to ignore moves, and the pickaxe (-S/-G) — and a rugged (libgit2) script that finds files often edited together. Highlights missing data: pull request provenance missing (conversations, cross‑repo links, Sentry/ticket correlations).

AI-written summary · about

" chapters (7)

1. 0:00Introduction
2. 1:58First principles in product design
3. 8:15Version Control systems
4. 14:54Git questions and limitations
5. 21:52Valuable Git commands
6. 27:56Impossible questions to ask
7. 32:10Call to action & Q&A

" related talks

• 35mGit: the stupid NOSQL databaseRick Olson · RubyConf 2010
• 49mUsing Git in Ruby ApplicationsScott Chacon · RubyConf 2008
• 31mConfessions of a Data Junkie: Fetching, Parsing, and VisualizationBobby Wilson · MountainWest RubyConf 2011
• 34mSource-Diving for Fun and ProfitKevin Kuchta · RubyConf 2019
• 29mBoring Ruby CodeAdam Niedzielski · Southeast Ruby 2017
• 29mTaking over Someone Else's Open-Source ProjectsDaniel Doubrovkine · GoGaRuCo 2014
• 05mLightning Talk: Git LintBrooke Kuhlmann · Blue Ridge Ruby 2026
• 35mHurting Code for Fun and ProfitRyan Davis · GORUCO 2008