A minor nit, the TL;DR is just an outline. I was hoping for a simple statement of the problem with a conclusion and the rest of the article would present the details, more of a real overview or synopsis.
> We would, for example, pick verbose over DRY if that results in code that’s easier to read and change. We have found that inheritance and mixins make change especially hard.
I disagree. We have a mixin heavy product (about 100k LOC) and the mixins, if designed judiciously, help ensure that we have good reuse of code. So I'd like to see some examples to support the case of "verbose over DRY", I haven't yet found that to be a "good thing(tm)", but some concrete examples could help.
I disagree. We have a mixin heavy product (about 100k LOC) and the mixins, if designed judiciously, help ensure that we have good reuse of code. So I'd like to see some examples to support the case of "verbose over DRY", I haven't yet found that to be a "good thing(tm)", but some concrete examples could help.