Duck Typing from POODR

Transcript

1. DUCK TYPING Continuing my talk on Sandi Metz's POODR
2. What are duck types? Simply, public interfaces that are not tied to any specific class (type).
3. But first, an example.
4. Good old Trip preparation
6. New Requirements – New Code
12. Consequences • We've moved from depending upon a concrete interface (Mechanic) to an abstract interface (the Preparer duck type) • Concrete – Easy understanding but hard to extend • Abstract – Tougher to comprehend but easy to extend (change) • Polymorphism!! --> Now is this what they taught us in college?
13. Where to use duck types? • When you see following constructs - – Switching on class – kind_of? And is_a? – responds_to? • “I know who you are and because of that I know what you do” - shows distrust on objects. • Look at the offending code's expectations and identify ducks.
14. Static vs Dynamic typing Read POODR.!
15. Some podcasts • Code Newbie • RubyRogues • JS Jabber • Full Stack Radio • BikeShed • Giant robots smashing into other giant robots