I'd like to get everyones opinions on Ruby tips and best practices.
He specifically mentions one point, monkey patching. Many books tout Ruby's dynamic nature and how you can use meta programming and open classes to create these cool DSLs, in the process they end up violating many OO programming principles.
I'd like to hear what design principles or Ruby constructs/idioms have been useful in real world experience. And what restraints should be undertaken to avoid shooting oneself in the foot (ex. Avoid using these constructs in this way for this reason)
For example, I think blocks in Ruby are awesome, and finally understanding them, a light bulb went on and all I can say is wow.
On Thursday, July 4, 2013 11:01:44 AM UTC-6, Garland William Binns III wrote: