In Duck Typing, an object's methods and properties determine its valid semantics rather than its membership in a particular class or its interface.

- Wiki
1 articles, 0 books.

Ruby likes ducks. Which is to say that when we're coding, and we have an object, we don't particularly care what kind of object it is, so long as it responds to the messages we send it. It might be a Duck or a Child or a Doctor, and as long as when we call #quack we hear a noise, all is well. That's called Duck Typing, and Ruby digs it.