It is unfortunately hard to convince someone once they’ve made up their mind.
But as long as people indifferent to the situation see my comment and get a fuller picture, I’m fine with it.
I tend to take a contrarian stance on a lot of things because if it turns out I’m wrong, people will correct me, and I learn something, so downvotes don’t bother me at all.
Yeah, a name should describe what it is or does, so if you have two turtles, and let’s say turtle1 wants to shit on turtle2’s lawn, you could name them shittingTurtle and victimTurtle. If the name alone tells you what its purpose is, that saves a lot of time for people looking at your code.
Is_Turtle is not a bad variable name because it tells you it is a Boolean with “is” and that the Boolean tells you whether something is a turtle or not.
Also, depending on the language, I suggest either camelCase or snake_case naming of variables. PascalCase is usually for defining classes or in case of C#, methods.