Code Spelunking: teach yourself how Rails works
summary
Shows that method introspection plus the Rails console and gems like method_source and byebug let you follow real execution paths, not just docs. Backed by a surprising stat—developers spend 82% of time on reading/navigation—and a Rails6 app ships with 77 gems and ~250k lines. Demonstrates a concrete build: thread the request_id through ActiveJob by overriding serialize/deserialize and confirming Sidekiq receives it, and the change works end to end.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 4:46How you spend your time
- 8:49What makes Rails difficult
- 12:37What is Code Spelunking
- 13:22Try vs Try
- 13:42Try bang
- 14:12Why do they both exist
- 15:06Foxley
- 15:17Console
- 19:10Try and Try
- 22:54Adding the request ID
- 25:22Job serialize
- 26:13Review
- 27:43Gem Code
- 29:42BaseNotExecute
- 31:14Conclusion
