Design better software abstractions using bipartite composition (2019)(cep.dev)
cep.dev
Design better software abstractions using bipartite composition (2019)
https://cep.dev/posts/design-better-software-abstractions-using-bipartite-composition/
7 comments
This feels unnecessarily fragmented and complex.
Sorry don't see the benefits of designing your classes in this fashion.
Sorry don't see the benefits of designing your classes in this fashion.
[deleted]
[deleted]
So the opposite of encapsulation?
No, this is just separation of concerns. Each thing that was separated is now encapsulated and can be reused in different places.
I've done this myself implicitly when trying to break down kitchen-sink classes. Often they were never really one class to begin with, so a lot of the contents can be separated into two or more new classes such that there are only a small number of dependencies between them.
SHIP : PHYSICAL OBJECT
On the surface this appears very “semiotic”