Prying Open The Black Box

on YouTube ↗37m

" summary

Shows how to turn a mystery Rails failure into a reproducible fix by following the stack trace, disable backtrace cleaner to see full frames, and inserting raises or prints (puts/pp) to get context. Demonstrates interactive inspection with binding.byebug and editing gems via bundle open active_record then restoring with bundle pristine, using git blame (with the ^ trick) to find intent, and generating a fresh app (dev flag) or a minimal bug template to isolate and fix the issue.

AI-written summary · about

" chapters (9)

1. 0:00Start
2. 3:31gem install canada
3. 4:03Software Writer
4. 5:45Black Magic
5. 7:02Pry Open The Black Box
6. 7:17Take a deep breath
7. 8:34Documentation
8. 14:23Backtrace Cleaner
9. 22:11bundle open GEM_NAME

" related talks

• 29mFilling the Knowledge Gap: Debugging EditionMina Slater · RailsConf 2019
• 26mDebugging Rails ItselfSean Griffin · RailsConf 2018
• 42mDissecting Ruby with RubyRichard Schneeman · Wicked Good Ruby 2013
• 37mDon't touch that!Adam Cuppy · RailsConf 2022
• 29mYes, You Can Work on Rails & any other GemKasper Timm Hansen · RailsConf 2025
• 34mCode Spelunking: teach yourself how Rails worksJordan Raine · RailsConf 2019
• 38mSpelunking in RubyJason R. Clark · Barcelona Ruby Conference 2014
• 39mPerusing the Rails Source Code - A Beginners GuideAlex Kitchens · RailsConf 2017