Instant code navigation for any commit ☠️
summary
Describes a solution for instant code navigation for any commit when reviewing pull requests in web interfaces. Names the problem: web code viewers lack proper IDE-like navigation, and proposes an approach to provide full, immediate navigation across commits (integrating with web PR platforms) to avoid switching to a local IDE.
AI-written summary · about
chapters (28)
- 0:00Introduction
- 1:54Introducing Source platform
- 3:01Code navigation limits
- 4:24Commit navigation challenge
- 6:10Requirements and trade-offs
- 7:18Compiler-based approach analysis
- 9:23Yandex internal solution
- 10:04GitHub text search limits
- 12:32Benchmark setup
- 13:16First implementation MVP
- 15:29Commit index structure
- 17:45Direct vs inverse indexes
- 19:11Implementation details
- 21:45Trigram index explanation
- 23:57Trigram index for commits
- 25:20First solution summary
- 26:00Improving local resolve
- 27:45Language clarifications
- 28:06Global LVA compiler
- 29:10Package member index
- 30:14Snapshot and delta strategy
- 32:19Snapshot placement logic
- 33:46Inverse deltas concept
- 34:49Second solution improvements
- 35:11Benchmark results
- 36:14Related research
- 36:58Team and thanks
- 37:20Q&A
related talks
48mInstant Code Navigation for Any Commit ☠️
46mIncremental, zero-config Code Nav using stack graphs
04mLive Coding
54mVersion Control in an IDE – What Should It Look Like?
47mLet the IDE do that for you
16mOptimize Your Code Reviews with Interactive Rebase!
29mCode review, do you speak it?
36mCommit Messages to the rescue!