Who Wants to be a Ruby Engineer?
summary
A live game-show format tosses short Ruby snippets at contestants who must guess exact outputs, with surprises drawn from method_missing surprises, operator precedence traps, and odd return-value rules that flip assumptions. Code comes from obscure corners of Ruby, often three- to five-line examples that reveal one concrete gotcha and the minimal change that fixes it. Audience members play along and answers are judged on correctness, not explanation.
AI-written summary · about
chapters (5)
- 0:00Welcome and introduction
- 5:50Why Ruby engineering?
- 21:23Contest rules explained
- 39:56Debate on Ruby’s future
- 57:16Final thoughts and thanks
