Duck Typing

Based on chapter #5 of POODR.

Given at rubygdl.org.

Transcript

1. Duck Typing @ruby_gdl << @solojavier # Based on chapter 5 of book poodr.com
2. What is Duck Typing "If an object quacks like a duck and walks like a duck, then it's a duck" Technique that help us reduce cost of change Public interfaces not tied to any specific class Duck typed objects are chameleons that are defined more by their behaviour than by their class
3. Learning by example
6. requirements.change!
9. code_design.add(:duck_typing)
13. Summary Duck typing detaches public interfaces from classes It creates virtual types defined by behaviour Depending on this abstractions increases flexibility This will make your application easier to change