This type of question, despite my own dislike of them, is actually on-topic on Programmers.
That said, such questions go against one of the main facets of Good Subjective, Bad Subjective:
Great subjective questions tend to have long, not short, answers. The best subjective questions inspire your peers to share their actual experiences, not just post a mindless one-liner or cartoon in hopes of being rewarded with upvotes for being merely “first.” Sharing an experience takes at least one paragraph; ideally several paragraphs. If I’m asking about how to bake cookies, don’t give me a list of grocery items: milk. butter. vanilla. eggs. There is virtually nothing I can learn from a short, static list of grocery items that make up a recipe. Instead, tell me what happened the last time you made cookies from that recipe! Share your detailed experiences, so that we all might learn from them.
Asking "what do I call this thing so I can go somewhere else and ask about it or search for it like I know what I'm talking about" is such a weak question: it'd be far better if you asked about whatever problem you're having directly and learn what it's called as a consequence of experts using it in the context of solving your problem.
To put it another way, what is the problem you're having that has you thinking about what exactly to call the concept? Why aren't you asking Stack Overflow or Programmers about that instead?