Open jrgifford opened 10 years ago
solution: do pseudo code for the explanation, saying "this is whats going on behind the scenes". Or better yet, use ri to inject itself into it to find out what the heck it's actually doing, and show them how to use ri and rdoc to find things.
and here's what I mean by that. http://www.jstorimer.com/blogs/workingwithcode/7766081-5-reasons-you-should-use-ri-to-read-ruby-documentation
Update this to reflect what the codebase looks like here