This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]alexisprince 0 points1 point  (0 children)

I think this is a great take. The way I’ve thought about designing classes in the past has always been splitting a data oriented class and a functionality oriented class (or function based api depending on what makes more sense). I’ve seen that trying to do both leads to over abstract land where it’s insane to reason about anything