My friend suggested I use different names for variables..

Try assembly language! You have registers, and they are named for you with highly memorable names like R17.

- RIP.
  Don’t recommend using that register to store your variables.

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.

SHOUTING_SNAKE_CASE aka SCREAMING_SNAKE_CASE is the best case for all use cases, because it gives you a chance to use its wonderful names.
- I prefer REVERSEcAMEL
I'm gonna be honest I just used Turtle ad an example:X .. when it's actually like a GoldCost, GoldC and GoldH. Where GoldR is a reset var and GoldC is the paid value. GoldCost is self explanatory but I really spagettied it up XD...
Thank you for this. This is awesome.
shittingTurtle and victimTurtle are going into one of my professional slide decks as soon as I think I can get away with it.

An array?

var turtles = new Turtle[] { new Turtle(), new Turtle() };

Don't do this :P

But I like tautological variable names
also turtles

Have you considered using inheritance?

blew my inheritance on hookers and blow, now what?
- Have you considered multiple inheritance. It's an upgrade. All upside, literally no downside. I'm trustworthy. Trust me.
I'm an amateur I'm not sure what inheritance is:X? Is it like instantiateing?
- When you start learning about different paradigms, you'll likely learn much more about inheritance when learning about the Object Oriented design paradigm.
  To overly simplify, you create objects that inherit attributes from other objects. It's for instance a way to create reusable patterns, that have stronger and more reliable data structures.
  I made the joke comment, because for instance, you could create a Turtle class, and always know it was a Turtle. Again, an oversimplification.
  EDIT: I should also add that for some reason OOP is an oddly divisive subject. Developers always seem to want to argue about it.

Fucking mathematicians

What's wrong with making a recursive function in a recursive function with variables M, m, N, n? It's perfectly fine when I'm writing infinite series.
- If we're talking mathematicians, you just know it's going to be ω-nested recursive functions any moment now. Just be grateful it's not all n with polynomial subscripts or something.

I always make sure my variables are named in ways I can remember what they're for. The only time I just use generic var1, var2, etc is if I am experimenting with a function I've never used before and wanna play around with it to see how it's used.

This should be easily read by others but there could be times where it's an inside joke.

Wait, what do you mean x3, y2, and x37 are not good variable names?

This is a very cute thread. I love turtles and I like them for their vast computer science skills too.

Based LOGO programmer.

All great code started out as a shitty work-around that happened to work.

(I say this as someone with one of the more prestigious pedigrees in "not writing shit code". All the theory I've learned helps, but at the end of the day the most important qualities of a line of code are: whether it got the job done, and whether is was obviously correct enough that the next developer left it alone.)

Because I mostly (almost exclusively) write shell scripts, my vars are often like this: theList, workingDir, etc.

I'm a monster. But it works for me.

Vedal made this post

Who? I made this you can tell by the imgflip in corner and PNG spaghetti xD...
- T'was a joke. He's a programmer guy on Youtube who uses a turtle avatar.

I remember an old mentor programmer I had who basically described his job as building an addition to an addition to an addition on a tree house built in a twig.

All these jokes about naming variables and yet no serious suggestions that if you have a turtle2, what you really need is a turtle array. I like to block out all the memory I'll need for the whole program up front, put it all in one big array, and then I can use clean, easy to remember numbers for all my variables!

Yes, its code whether it executes or not.

The word 'code' has many different definitions. The shaolin martial arts tournament is governed by a system of rules of conduct
...an ethical code.
The combatants respect each other as warriors, no matter what degree of hatred they have for one another
...a code of honor.
Another type of code could be defined as an arbitrary system of symbols or letters for transmitting messages
...a secret code.
Mortal Kombat(tm) adheres to many codes, but does it contain one?
- Yes, more code

Yes your variable names should indeed all be different from one another.

var Turtle1 var Turtle1 var Turtle1

just doesn't quite have the same impact:-).