News for hackers. Stuff that matters.
Re:Why you should never ever ever have Managers in your clas... by Lagged2Death on Sunday March 31, 2013 @08:58PM (#5470878)
It makes me feel pretty dense to admit this, but I don't see the connection (ha) between this basic good advice (use short, precise, descriptive class names -- certain classes of names are a warning sign) and the famous "Kingdom of Nouns" essay the author is so eager to have us read. Because a "ThingManager" is still noun-style all the way, even if you rename it to "Thing."
Re:Why you should never ever ever have Managers in your clas... by BIackSwan on Sunday March 31, 2013 @09:17PM (#5470935)
The "Kingdom of Nouns" essay is about the forceful enforcement of Nouns even when they aren't entirely necessary. As a consequence of this thinking, it has led to the rise of use of -Manager classes even when not required.

More importantly, the acceptance in the developer community that its ok to define large number of classes with that name is just a bad influence. Noun style is not a bad thing at all. Its just that when you think of everything as Nouns that things go downhill (which lead to naming things -Managers, -Handlers etc).

Re:Why you should never ever ever have Managers in your clas... by Lagged2Death on Tuesday April 02, 2013 @02:29PM (#5481205)
...when you think of everything as Nouns that things go downhill (which lead to naming things -Managers, -Handlers etc).

Yeah, not seeing it. If I "think of everything as Nouns" then I might go with "Noun" or "NounManager" as a name - but they're both nouns, and I don't see how pointing that out helps.

I completely agree with the point that "Manager" style classes are a warning sign that something could be usefully refactored. But if you're just going to refactor stuff into other nouns, and you're trapped in a noun-centric language anyway, I don't see any real connection between the advice on the one hand and the message about how trapped I am on the other.