var Turtle1 var Turtle2 var Is_Turtle
Try assembly language! You have registers, and they are named for you with highly memorable names like R17.
ngl RAX actually sounds cool and is memorable 🥺
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
Thanks. I hate it.
I consider myself a collector of programming anti-patterns, but I didn’t have this one yet.
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.
shittingTurtleandvictimTurtleare 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.
Idunno, my mom told me not to talk to _stranger_s 🤔
… She said a lot of things that were BS, though, so maybe you’re cool I guess? 🤷
You might not like it, but that is what peak shareholders value looks like.
Wow. “peak shareholder value” is what I shall now call “multiple inheritance”, from now on.
I like it. I’d let you serve as a CTO at my beloved corp
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
Turtleclass, and always know it was aTurtle. 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.
At this point I think there is no software dev topic that is somehow not devisive.
At this point I think there is no software dev topic that is somehow not devisive.
Now I want to try something:
“Boolean variables don’t suck.”
No one uses Boolean values anyway and with the amount of resources available on modern systems we can just replace them with integers and we should be fine. This also makes it easier to teach people, as they would learn less different data types.
Yes I’m a software dev :)
I love it!
Oh yea, class resources. That would work! Thanks.im going to have to into this more, as it’s going to be useful
Just keep in mind that inheritance is nowadays a very contested feature. Even most people still invested in object oriented programming recognise that in hindsight inheritance was mostly a mistake. The industry as a whole is also making a shift to move more towards functional programming, in which object orientation as a whole is taking more of a backseat and inheritance specifically is not even supported anymore. So yeah, take the chance to learn, but be cautious before going into any one direction too deeply.
I like to mix between OOP and FP for different levels. OOP is great for higher architectural problems. FP is great for everything under it.
And yes, inheritance was a huge mistake. Just use composition and interfaces instead.
Yeah, I mix them too, although I apply quite a bit of functional techniques especially at the architectural level as well. OO I use mostly for dealing with I/O and other areas where statefulness cannot be avoided.
If you’re interested, I also wrote an in-depth blog where I touch on these topics: https://arendjr.nl/blog/2024/07/post-architecture-premature-abstraction-is-the-root-of-all-evil/
If I could give a suggestion I wish I had gotten much earlier on in my education and career, it would be to really spend some time learning about the different paradigms, and their best use cases. You will likely ensure yourself a strong foundation in software architecture.
I’ll check it out! I’m very casual and doing thus mostly as a passion/Fun project. But I love any direction thank you:)
Inheritance established “is a” relationship between classes.
class Turtle; class TigerTurtle is a Turtle (but better); class BossTurtle is a Turtle (but better);Underlying classes hold an inner object to the super class, everything from Turtle will be in TigerTurtle and BossTurtle.
In some languages that is configurable with public, private, protected keywords.
Relatedly, there’s also composition, which establishes a “has a” relationship:
class TurtleTail; class Turtle: var tail: TurtleTail; (has a tail);Since Turtle is NOT a tail, but a whole animal, turtle should not inherit TurtleTail. But it HAS a tail, thus we add turtle tail as a property.
I’m only commenting because the actual python is practically pseudo code:
# A turtle class class Turtle: shell=True # A boss class class Boss: authority=True #A class that inherits from another class TigerTurtle(Turtle): fuzzy=True # Multiple inheritance, or "The Devil's Playground" class TigerBossTurtle(TigerTurtle, Boss): # shell, authority, and fuzzy are all true ...It is simpler than my faulty memory remembers, time to learn python again 😁
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.
Polynomial subscripts sound awesome, ngl. Never seen it before; I want to know what the applications are.
Uhh, I’m pretty sure I’ve seen that, but I’m not sure where now. Any time you need to access a member of a list or array that’s determined by a polynomial - which by Horner’s rule covers all combinations of multiplications and additions - it would be a possible notation.
Transfinite algorithms are definitely a topic of research.
Based LOGO programmer.
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.
This is a very cute thread. I love turtles and I like them for their vast computer science skills too.
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.
Wait, what do you mean x3, y2, and x37 are not good variable names?
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.)
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 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:-).
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™ adheres to many codes, but does it contain one?
Yes, more code
