-
Jeremy Evans
3.11
Description:
Many presentations focus on showing off new applications and libraries. They show you what has been accomplished, but rarely do they show you how. This presentation will take examples from production code (mainly from Sequel), showing techniques that you can use in your own code. Some of the techniques demonstrated will relate to:
- Creating more easily extensible code
- Handling class-level data within inheritance hierarchies
- Improving dynamically defined method performance safely
- Structuring DSL implementations
- Presenting multiple backends as one
Comments on this Talk
osake,
16 Jul 06:32 PM
Interesting topic, but delivery needs some work and definitely felt confined by the format (30 minutes). I'd like to see this one in a hands-on workshop with at least another hour dedicated to it.
cdumler,
16 Jul 06:43 PM
Less would be more. The value of the presentation was creating better code, but the details of Ruby's intricacies was not needed. Instead of all the "superclass's metaclass's parent class subclass is..", I would say "There is complexity due to how Ruby's module system works. If you want to write code that can be flexibly included and methods overwritten, do this!" The value of the presentation was very good. Going to spend time trying to wrap my head how the code works. Impressive.
Kyle Heironimus,
17 Jul 03:35 AM
Good, but would have been better with more depth in fewer examples. Showed a screenful of code for 15 seconds, then expected us to soak it in and understand it. There were several cool tricks, though. Definitely glad I heard the presentation.
Alex Sharp,
17 Jul 08:33 PM
Being someone who has never used sequel, I appreciated seeing some really nice code. I agree, some of the object model stuff moved a bit quick, but all in it was a solid talk that showed great code examples (which, to me, is always a win).
markborcherding,
20 Jul 02:05 PM
Even as a non-Rubyist the concepts clicked and made sense.
jgchristopher,
20 Jul 02:23 PM
A Class is a Class of course, of course, unless of course the Class is a SingletonClass ...
This talk was awesome!

Covered some really DEEP language concepts in 30 minutes. 30 minutes isn't a lot of time and the required base understanding was high.
Content would have benefited from a graphical representation of some of the class instance override-able methods verses the text heirarchy representation.
Delivery was a little unnatural/dry but content was spot on.
Class Instance Class Module Class Class.