2 ms·
I suspect OP is confusing number of attributes with number of abstraction layers. Attributes are not a problem as long as they're listed with intent and not ju
by TheOtherHobbes 6y ago
I suspect OP is confusing number of attributes with number of abstraction layers.
Attributes are not a problem as long as they're listed with intent and not just thrown into a bucket, and there's some rationale for their existence.
It's much harder to trace flow down and up through multiple abstraction and encapsulation layers. And it's harder still to remember the layers for different classes/applications. And it's even harder to do this when all the class names are related and hard to tell apart.
- pbw 6y agoHierarchy and abstractions have costs, no doubt. I didn't get into that in the article, but the article was only 1500 words. I can imagine a long "yes, but..." section that explores the risks and downsides of small objects. It's possible to write total crap software using only small objects for sure. I don't advocate doing that. That's where the Bonsai metaphor comes in, that's as much about shaping and pruning as growing. Uncontrolled growth of small objects has a name: cancer.