Context Buddy: the tool that knows your code better than you
summary
A prototype called Context Buddy reconstructs token-level history (not just git blame) and plugs into IntelliJ using semantics-db and zinc traces to show which symbol or type changes actually affected a line. Demos include a broken cache revealed by a mutable->immutable map import, a Set→Seq type change that altered outputs, a time-library downgrade from a jar eviction, and implicit/autotuple changes. Data comes from CI and local compiles, it suggests who to ask and which commits or reviewers introduced the change, and it’s available for private trials.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 2:30Context Buddy
- 4:03Why use Context Buddy
- 6:00Incremental compiler
- 11:04Fossilized burrow
- 15:49Footprints
- 16:34Coat
- 17:54Map
- 19:44User Interface
- 24:09Inspection
- 25:39Scala
- 26:49How to try it
- 28:19Future of Context Buddy
- 31:59Conference factor
- 36:06Compilation errors
- 41:17Questions
