var Turtle1 var Turtle2 var Is_Turtle
- henfredemars ( @henfredemars@infosec.pub ) English33•7 days ago
Try assembly language! You have registers, and they are named for you with highly memorable names like R17.
- ma1w4re ( @ma1w4re@lemm.ee ) 8•7 days ago
ngl RAX actually sounds cool and is memorable 🥺
- henfredemars ( @henfredemars@infosec.pub ) English3•7 days ago
RIP.
Don’t recommend using that register to store your variables.
- parpol ( @parpol@programming.dev ) 17•7 days ago
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.
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…
- MajorHavoc ( @MajorHavoc@programming.dev ) 2•7 days ago
Thank you for this. This is awesome.
shittingTurtle
andvictimTurtle
are going into one of my professional slide decks as soon as I think I can get away with it.
- Dr. Wesker ( @wesker@lemmy.sdf.org ) English7•7 days ago
Have you considered using inheritance?
- metaStatic ( @metaStatic@kbin.earth ) 15•7 days ago
blew my inheritance on hookers and blow, now what?
I’m an amateur I’m not sure what inheritance is:X? Is it like instantiateing?
- Dr. Wesker ( @wesker@lemmy.sdf.org ) English4•7 days ago
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 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.
Oh yea, class resources. That would work! Thanks.im going to have to into this more, as it’s going to be useful
- arendjr ( @arendjr@programming.dev ) 3•7 days ago
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.
- arendjr ( @arendjr@programming.dev ) 2•7 days ago
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/
- Dr. Wesker ( @wesker@lemmy.sdf.org ) English1•7 days ago
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:)
- ma1w4re ( @ma1w4re@lemm.ee ) 3•7 days ago
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.
- r00ty ( @r00ty@kbin.life ) 6•7 days ago
An array?
var turtles = new Turtle[] { new Turtle(), new Turtle() };
Don’t do this :P
- Hupf ( @Hupf@feddit.org ) 5•7 days ago
But I like tautological variable names
also turtles
- 🇰 🌀 🇱 🇦 🇳 🇦 🇰 ℹ️ ( @Kolanaki@yiffit.net ) English4•7 days ago
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.
- some_guy ( @some_guy@lemmy.sdf.org ) 3•7 days ago
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.
- NigelFrobisher ( @NigelFrobisher@aussie.zone ) 3•7 days ago
Based LOGO programmer.
- SteevyT ( @SteevyT@beehaw.org ) 3•6 days ago
Wait, what do you mean x3, y2, and x37 are not good variable names?
- MajorHavoc ( @MajorHavoc@programming.dev ) 2•7 days ago
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.)
- sheepishly ( @sheepishly@fedia.io ) 2•7 days ago
Vedal made this post
Who? I made this you can tell by the imgflip in corner and PNG spaghetti xD…
- sheepishly ( @sheepishly@fedia.io ) 2•7 days ago
T’was a joke. He’s a programmer guy on Youtube who uses a turtle avatar.
Ahh ok:p my bad xD… I was like I made this shitty meme no way someone stole it!
- OpenStars ( @OpenStars@discuss.online ) English2•7 days ago
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:-).