Deep diving: how to explore a new code base

on YouTube ↗32m

" summary

Goal-driven approach to learn MRI Ruby by fixing a real bug: reproduce a Nil proxy behavior in open-uri, trace the execution with TracePoint and the tr_calls gem to produce a call graph, inspect ~100 relevant lines (out of ~3,000) instead of reading everything, run targeted tests via bundle, change a single buggy line, and submit a patch and bug report — whole cycle takes about two hours and the fix lands.

AI-written summary · about

" chapters (8)

1. 0:00Introduction to code exploration
2. 4:40Planning your code dive
3. 7:51Finding project maps and guides
4. 13:13Setting up your environment
5. 16:27Reading code efficiently
6. 18:59Tracing code execution
7. 27:19Fixing the bug example
8. 29:27Choosing good goals

" related talks

• 26mDeep Diving: How to Explore a New Code BaseChristophe Philemotte · eurucamp 2015
• 42mDissecting Ruby with RubyRichard Schneeman · Wicked Good Ruby 2013
• 38mSpelunking in RubyJason R. Clark · Barcelona Ruby Conference 2014
• 01h 22mBreaking Down the Barrier: Demystifying Contributing to RailsEileen M Uchitelle · RailsConf 2015
• 37mPrying Open The Black BoxGodfrey Chan · RailsConf 2015
• 34mCode Spelunking: teach yourself how Rails worksJordan Raine · RailsConf 2019
• 39mPerusing the Rails Source Code - A Beginners GuideAlex Kitchens · RailsConf 2017
• 30mCome on in! Making yourself at home in a new codebaseMercedes Bernard · RailsConf 2022