Boring Ruby Code
summary
Shows concrete GitLab code where metaprogramming like define_method, method_missing, const_get and a redefined [] operator hides where behavior lives, wastes about 30 minutes chasing alpha_rise_download_code via grep, and leaves dead or untested hooks that rarely get removed. Demonstrates replacing hidden dynamic dispatch with simple extracted methods, shows respond_to checks spreading conditionals across call sites, and argues that simple, repetitive, boring code is easier to read, delete, and maintain than clever abstractions.
AI-written summary · about
chapters (8)
- 0:00Introduction to boring code
- 6:56Smart code examples
- 11:57Metaprogramming pitfalls
- 15:55Method missing misuse
- 19:18Redefining operators
- 20:53Overly complex methods
- 25:32Existential type checks
- 26:37Why boring code matters
