Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 158 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

Are questions concerning class names relevant on any of the Stack Exchange sites?

I'm not referring to discussions about the merits of one naming convention over another. But, questions actually referring to the meaning of a class name and what would be most appropriate.

For example, I have a question in regards to naming a domain object. I am working with a publicly available API that returns back a User object with a lot of data. They also return back a Follower object with not quite as much data. I have a question in regards to what would be the most appropriate way of naming, and dealing with, these different domain objects; keeping in mind that a Follower is really just a subset of User and that other non-Follower objects return exactly the same information. Perhaps the answer leads to something other than a naming issue but the point is that the initial question is one about naming classes.

Is this appropriate for any of the Stack Exchange sites and, if so, which one?

share|improve this question
I certainly hope there is. It sounds like a grey area between SO and Programmers, but I don't spend enough time on the latter to really know what's acceptable there. – David Feb 4 '12 at 22:06

In general, understanding the meaning of well-known programming terminology used in names would be on-topic for Programmers:

What is a delegate? What things count as delegates?

Similarly, understanding the appropriate use of design patterns (which would likely indirectly lead to answering a question about naming) would be on-topic for Programmers as well:

I'm working on X problem: would using the observer pattern be the most appropriate way to handle it?

And finding the correct terminology to describe a concept is usually on-topic on Programmers:

I've used this pattern that looks similar to other code I've seen, but I'm not sure how to refer to it so I don't look dumb in front of my coworkers

But many of these types of "concept naming" questions get too far into bike-shedding and neologisms and thus aren't constructive:

Can you think of a name to call this pattern I just made up?

Likewise, naming advice for your classes, methods, et al is not constructive anywhere, including Programmers. It ultimately rests on who's reading the code and what the internal naming conventions for the project are:

What should I call this method that does X?

Subsequently, understanding people's code would not be on-topic for Programmers (or Stack Overflow) either as it requires private knowledge about the intent of a person we don't know:

Why did my coworker name this method punchFluffyBunnies()?

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .