Design better software abstractions using bipartite composition (2019)

https://cep.dev/posts/design-better-software-abstractions-using-bipartite-composition/

by dmarto • 2 years ago

12 5 2 years ago

cep.dev

golyi• 2 years ago

This feels unnecessarily fragmented and complex.

Sorry don't see the benefits of designing your classes in this fashion.

turkey99• 2 years ago

So the opposite of encapsulation?

MattPalmer1086• 2 years ago

No, this is just separation of concerns. Each thing that was separated is now encapsulated and can be reused in different places.

jprete• 2 years ago

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.

xtiansimon• 2 years ago

“We can use composition to break our ship object into two concepts.”

SHIP : PHYSICAL OBJECT

On the surface this appears very “semiotic”

Design better software abstractions using bipartite composition (2019)

Related Stories