

9·
7 months agoFor me it depends on the use case. If I’m designing something with an interface for someone downstream to use, I’ll usually define (data)classes even if I have a functional interface.
For data science/modeling/notebooks I usually wouldn’t define classes.
I think it also depends on your team; if everyone else is a functional programmer and you’re writing classes or vice versa, this will undoubtedly create frictions.


Devil’s advocate: if the problems were could be solved with relatively simple programming, why aren’t why they solved already?