I don't advocate punting the complexity into a hierarchy of objects/types. Limiting yourself to seven attributes per object in not a panacea, you can create an

I don't advocate punting the complexity into a hierarchy of objects/types. Limiting yourself to seven attributes per object in not a panacea, you can create an utter shite design with small objects. We've all seen that. Let's turn it around. Do you feel that the more attributes in a class the better? So 10 is better than 5? And 20 is better than 10? I suspect not. I suspect you also feel there is a balance. I'm just saying that seven is an interesting number in the balance based on how our brains work. You want to make sure every additional object is pulling its conceptual weight. You want to make sure you minimize the accidental complexity while accommodating the necessary complexity. Balance in all things. Neither OOP or FP are cure-alls where if you just do those things you can turn off your brain and go on auto-pilot. Brain Oriented Programming is the same way, it's a guiding principle, it's something to keep in mind, but it's not so profound that it wipes out the need for good design judgment, engineering skills, or common sense.