I recently posted a question which got put on hold as being off topic. I since edited my question but it initialy went like that:
I need to name a configuration value that describes how much time a "session" lives on its own before it is either destroyed automatically or joined by at least one user.
I initially thought of
session_lifespan
but that does not convey the appropriate meaning: it refers to the maximum duration the session will live, regardless of whether somebody joined it.What is a good word or expression for such a concept ?
Somebody mentionned that questions asking for names for "progamming thingies" were off-topic: fair-enough. It's my fault after all for not reading the rules beforehand.
I edited my question to remove all programming related references, which then looked like this (pasted here to ease comparison):
I need to find a term that describes how much time an "entity" lives on its own before it is either destroyed automatically or becomes "used" (which implicitely prevents its destruction).
I initially thought of
entity lifespan
but that does not convey the appropriate meaning: it refers to the maximum duration the entity will live, regardless of whether somebody started to use it.What is a good word or expression for such a concept ?
I've read this question which states why asking for variable names does not fit English StackExchange and I actually agree with the community-approved rationale.
However, something still feels a bit off here:
- while my question indeed mentioned a programming-related context, it could easily be reworded to be programming-agnostic. I merely mentionned my goal to eventually provide some context (You won't define
crane
the same way if I tell you I use it to lift something or if I tell you I need to feed it every morning). - the few technical terms that were present in the initial version were probably not a barrier to understanding the question: the notion of session is not really programming-specific for instance.
- the reworded question basically asks for the same thing but I feel like it's abstract formulation makes it harder for people to grasp the exact nature of what's asked.
- in the end, I feel it shouldn't matter whether I need the expression to name a variable in a configuration file or a concept in fan-fiction novel.
- if I have some naming constraints due to size, programming language or company policy, then I agree this has nothing to do here and is ultimately my problem. Note that this wasn't the case here.
Ultimately, the word I was looking for was unclaimed
, which is not programming-specific (not that many words are anyway).
I'd really like to be a good citizen here and I fail to see how I should have asked my question.
Could someone define more clearly the line between: "it doesn't belong here" and "programming is just a context here" ? Should I always remove any programming context before asking how to name a thing in order to comply with the community rules ?
Susan
. It works just as well.