Why questions about naming are considered "opinion-based"?
If you working in the team you will spend some amount of your "productive" time on the naming.
I am pretty sure that every developer have moments when he struggling with names for new functions, variables, classes etc.
Proper names saves time for other developers who reads your code and even for yourself after few weeks.
When you see a class with a name
SomethingBuilder - you expects that this class will create new objects based on the arguments passed to the
When you see method with name
GetItem you expect that that method will return object without changing state of the context.
In case when you or your team cares about naming, naming become equally important as choosing design patterns.
Naming not based anymore on the opinion of developer - it based on the logic used in the method/class or output data.
If I can logically ground why one name can be more "effective", "readable" in particular case, than another, then, I think, it cannot be, so easily, considered as opinion-based anymore.
What should I name this thing?
Which is not a "guessing game" question; it is primarily opinion-based. There are literally an infinite number of such questions; none of them are at all interesting to experts unless they can be answered from a principle-based perspective, in a way that could help others improve their naming skills.
In my question I tried pointed out, that questions about naming with proper description of the problem can be considered as not opinion-based.
Questioner expects logically proved/explained reason for the suggested name in same way as question about "How/What pattern can be implemented in specific issue."