Gatekeeper Drainer Jockey

Wednesday 14 September 2005

After wrestling with the classic software problem of what to use instead of Manager when naming classes, Pete came up with a thesaurus-like list to help. My favorite is Jockey.

Comments

andrew 11:12 PM on 14 Sep 2005

Wrangler

Nate Finch 9:28 AM on 15 Sep 2005

Bah, if it's a manager, call it a manager. If it were something else, you'd call it something else. There are a lot of things to manage in a software product, so you're likely to have a lot of managers.

andrew 11:17 AM on 15 Sep 2005

What do you call the singleton that manages all of the managers? The Vice-President? The CTO?

Michael Chermside 12:48 PM on 15 Sep 2005

Andrew: The answer is "ManagerManager" of course. A consistant naming scheme is very useful. If you go this route, make sure that _all_ classes named FooManager are "manager" classes implementing the Manager interface and managed by the ManagerManager master class, and that all such manager classes have a name ending in "Manager". Given that you might already have some unrelated classes floating around that have "Manager" in the name, you might want to open up that thesaurus and select an alternate term. "ControllerController" might work...

Pete Lyons 10:19 PM on 15 Sep 2005

Andrew, the answer is actually QueenBee

Add a comment:

Name:

Email:

Ignore this:

Leave this empty:

Web site:

Name is required. Either email or web are required. Email won't be displayed and I won't spam you. Your web site won't be indexed by search engines.