duck typing is a style of dynamic typing in which an object's current set of methods and properties determines the valid semantics, rather than its inheritance from a particular class or implementation of a specific interface.
For you non-programmer types out there -- if it looks like a duck and quacks like a duck, it's a duck.
more at wikipedia if you're so inclined...
I particularly like this comic because it succeeds in simultaneously mocking one of the primary
arguments made by sometimes sycophantic proponents of those languages that rely heavily on duck typing (see ruby) to 'prove' why it's better than <fill-in-the-blank> language, while also getting a sly dig in on managers who either suffer from the Peter Principle, or who otherwise just phone-it-in.
No comments:
Post a Comment