Explanations with bad analogies are really a very often problem. Although this author matched monads with burritos relatively well. Except for the purpose - we

Explanations with bad analogies are really a very often problem. Although this author matched monads with burritos relatively well. Except for the purpose - we know the purpose of burritos, but this does not help to understand the purpose of monads (for programming, in particular). But sometimes a concept is named after a bad analogy by the concept authors (and probably even invented after that bad analogy, although maybe the authors just use poor name because they fail to clearly recognise the essence of their solution). Like mixins. I satirise that in my Mixin FAQ Q: What is a mixin? A: Mixin allows to inject functionality into classes. Mixins first appeared in the Flavors system and were inspired by an ice cream shop offering a basic flavor of ice cream (vanilla, chocolate, etc.) with a choice of optional "mix-in" ingredients like nuts, cookies, candies, etc. Q: Can I mix-in a ServerSocket into a ColorPicker? A: Yes, why not. Q: How will it work? A: Like ice cream with cookies.