Design better software abstractions using bipartite composition (2019) (cep.dev)

This feels unnecessarily fragmented and complex.

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

So the opposite of encapsulation?

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.

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

SHIP : PHYSICAL OBJECT

On the surface this appears very “semiotic”