6 ms·
> any time you have a vaguely specified component with "manager" in its name This seems to be a limitation of class based OOD and the absence of free standing
by 0x445442 4y ago
> any time you have a vaguely specified component with "manager" in its name
This seems to be a limitation of class based OOD and the absence of free standing functions. There needs to be a place for code to exist which operates on disparate data types and structures. I’ve found that creating singletons that replace the word Manager/Utility with Lib doesn’t offend the sensibilities as much.
- buescher 4y agoYes - to be clear, the limitation is the notion in the methodologies (not necessarily the underlying language) that any time something has to happen, an object does it. Should it be this object? No, it should be a different object. What should we call it? Yes, I was making a funny about Conway's law, but that's the point you shrug and say "call it pointAToPointBConnectionManager".
- zozbot234 4y ago> the notion in the methodologies (not necessarily the underlying language) that any time something has to happen, an object does it. That's not necessarily a bad notion, though. It's pretty much the definition of a capability, which is an important concept when designing for modularity.